Fix verbatim parsing to be unambiguous #385
Merged
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
With the previous parsing, it would interpret
```
emitc.verbatim "#endif // PL_USE_XRT"
%4 = "emitc.constant"() <{value = 1 : i32}> : () -> i32
```
as if
```
emitc.verbatim "#endif // PL_USE_XRT" %4
= "emitc.constant"() <{value = 1 : i32}> : () -> i32
```
and then complain that it expected a `:` after the `%4`.
Fix this by introducing a `args` keyword to distinguish the case where the veratim has args
from the case where the next operation starts.
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.
With the previous parsing, it would interpret
as if
and then complain that it expected a
:after the%4.Fix this by introducing a
argskeyword to distinguish the case where the veratim has args from the case where the next operation starts.