Add deprecation warning to bad uses of lit() #1236
Open
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.
I'd really like to rewrite the parser and make its uses cleaner.
FN_LITERAL
, which is only used bylit()
, is a big pain in my posterior because of how it alters the parser.I'd like to switch
lit()
fromFN_LITERAL
toFN_NOPARSE
. This PR is a first step - iflit()
is called with mismatched, unescaped {}s or []s, this will simply warn executor and enactor.