-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Better "unexpected kw" handling in ternary parsing #77
Conversation
2915bd9
to
424be21
Compare
424be21
to
15c028c
Compare
c883efa
to
7b6ad27
Compare
Co-authored-by: Kristoffer Carlsson <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is fine, as far as it goes.
I've been procrastinating about doing this review because I want to do error reporting more like I've vaguely outlined in #93.
But to motivate a general system like #93 we do need a bunch of specific use cases like this, #92 and all the other specific error messages which are hardcoded in various places.
So as long as error recovery is clearly marked and doesn't cause large scale disruption of the parser I think we can add it piecemeal for now.
end | ||
|
||
# FIXME: This is a very specific case. Error recovery should be handled more | ||
# generally elsewhere. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
aha agreed! This is why I've been wondering what to do about this PR.
No description provided.