check for parse/token errors and print them on run #8586
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
Acepie
commented
Dec 7, 2025
Anton-4
previously approved these changes
Dec 8, 2025
Contributor
Author
|
Looks like CI failed cause of a conflict with https://github.com/roc-lang/roc/pull/8562/files#diff-3f7ed75ee7d098e3068816b0a056374a527e8a05ce6595cfc9255fdd0ebd6d26L16 should be fixed now hopefully |
Anton-4
approved these changes
Dec 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes #8584
It looks like during roc run we don't check for token/parse errors. This adds a check to see if there are any errors from parsing and dumps the reports to the terminal. It also uses the same error count mechanism to exit early if the user does not pass
--allow-errors.