[Core] Implement special escape functions (through ParseSingleUnsafe)
#22
Conversation
This file contains 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
- Implement `Pull()` on the language level to allow "dismissing" state of calling - Add unit tests - [CentralSnippets] Fix parsing call
- Clean and update unit tests
- Illustrate the point that `Parse()` bypass itself when interpreted.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Implements special handling for
Parse()to allow state discontinuity: whenParse()is executed on its own, we will "dismiss" the content being parsed and effectively "insert" the states from execution of the interpreted script. This is illustrated in the commit 8b610fc.