-
Notifications
You must be signed in to change notification settings - Fork 6.1k
[Yul] introduce break/continue keywords. #6136
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
Conversation
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.
We should be careful not to merge this before the optimizer can cope with it (or at least put assertions in the appropriate places).
Perhaps to simplify this, as a first step one could add full support to the parser and rejecting it in the analyser. I think that would be safe to merge even now, without the need to update optimisers. |
2b2ee2e
to
77586e9
Compare
6d9c530
to
017c1f2
Compare
80e28d4
to
5d6b0f8
Compare
fcd943e
to
14ebc1c
Compare
This comment has been minimized.
This comment has been minimized.
f16fa65
to
88469cb
Compare
done, so far. (more changes still pending, still in WIP-status)
23b3cdd
to
72fc5f9
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
e211913
to
764f4e4
Compare
75e7758
to
bf17f5f
Compare
bf17f5f
to
05e2d36
Compare
This PR implements
break
andcontinue
keywords in Yul. (refs #4576)Checklist