Repository navigation
feat: bracket diagnostics and readable parser errors (#30, #38) - #93
Merged
Merged
Conversation
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.
Parser::check_bracketsreportsline:col: unclosed '['andline:col: unmatched ']'(unclosed brackets used to compile silently)expected Else_ but found Eofnow readsexpected 'else' but found Eof(keyword spelling from the source)moon test --target js337/337; all 13 examples and all 53 get-started lesson files still passcheckwith no errorsThe language server (#92) already parses these
line:colmessages. Still open in #30/#38: AST node spans, multiple recoverable errors, error codes, source maps.