-
-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Towards error resilient frontend #5036
Comments
@Pranavchiku as we discussed:
I think we should for now not add error nodes into the AST/ASR, that can be done later if needed, and perhaps it is not needed. |
Yes, I just copied it over so that I can brainstorm and document design ideas here whenever I do. |
This was referenced Nov 2, 2024
This was referenced Nov 7, 2024
This was referenced Nov 9, 2024
This was referenced Nov 10, 2024
This was referenced Nov 13, 2024
This was referenced Nov 17, 2024
This was referenced Nov 19, 2024
This was referenced Nov 24, 2024
This was referenced Dec 3, 2024
This was referenced Dec 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Picked from PR: #1098:
This example shows how to recover from errors, it creates an AST:
TODO:
The text was updated successfully, but these errors were encountered: