Support placeholder holes and prompt for implicit values when needed #115
Merged
Conversation
Member
Author
Member
Author
|
When a parameter value is needed at an invocation point the prompt becomes showing the variable to be bound and its type, asking for a value (and accepting for a default). Obviously we don't have type construction defined yet, but passing a string literal Value serves well enough for now. |
istathar
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Improve presentation of procedures when running.
Introduce support for placeholder holes implicitly defined when invoking a procedure requiring input parameters. This is done when running by prompting the user to supply a value when invoking.
Correctness improvements related to Quitting and when + interrupted.