Precise error location in UNRECOGNIZED by attaching trivia to the expected nonterminal #1172
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
🦋 Changeset detectedLatest commit: 72d4858 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Likely this deserves a changeset, since it's changing the way an UNRECOGNIZED node is return when it's in the top-most position. |
OmarTawfik
reviewed
Dec 6, 2024
crates/codegen/runtime/cargo/crate/src/runtime/parser/parser_support/parser_function.rs
Show resolved
Hide resolved
OmarTawfik
reviewed
Dec 6, 2024
...snapshots/cst_output/ContractDefinition/unicode_in_doc_comments/generated/0.4.11-failure.yml
Show resolved
Hide resolved
OmarTawfik
reviewed
Dec 6, 2024
...snapshots/cst_output/ContractDefinition/unicode_in_doc_comments/generated/0.4.11-failure.yml
Show resolved
Hide resolved
OmarTawfik
reviewed
Dec 6, 2024
OmarTawfik
reviewed
Dec 10, 2024
crates/codegen/runtime/cargo/crate/src/runtime/parser/parser_support/parser_function.rs
Show resolved
Hide resolved
OmarTawfik
approved these changes
Dec 11, 2024
This was referenced Dec 11, 2024
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.
Fixes #841
In examples like the following:
The parsing function was returning a terminal with
UNRECOGNIZEDkind and the entire text inside. Since a terminal cannot have trivia attached, we have to change the returning value to be a nonterminal. But which one? For a moment I thought of a new specificUNRECOGNIZEDkind, but after discussing with Omar, it was clear that the better option was to return the expected one: if we are parsing aStatement, then return aStatementwith the trivia and theUNRECOGNIZEDterminal at the end. This is realized in theNoMatchstructure with a new field for the optional expected nonterminal kind, which is essentially attached in theParserResult::with_kindmethod.The commit history contains a previous attempt in which the trivia was cached within the
NoMatchstruct. This added unnecessary complexity, so I decided against it.Note1: In a couple of places the code will use a
ParserResult::no_match(<default values>). Noting there was aParseResult::default()function, I decided to use it instead, but I'm not sure if this is the expected use of the default function.Note2: I see that the error is one off at the end, probably accounting EOF? But was already the case before, so there's no real change there.