-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
fuse < and > with = when applicable #78786
Conversation
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsFixes #78385
|
@EgorBo PTAL |
@pedrobsaila could you please merge/rebase recent Main into your PR so we can get the recent diffs? |
/azp run Fuzzlyn |
Azure Pipelines successfully started running 1 pipeline(s). |
@pedrobsaila sorry for the delay, overall looks good to me, can you rebase it once again please? |
/azp run Fuzzlyn |
Commenter does not have sufficient privileges for PR 78786 in repo dotnet/runtime |
Ping @EgorBo for one more review. |
@pedrobsaila, please resolve the conflict. |
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.
Sorry for the long delay - LGTM, I see that we can check LCL_VAR by its num here since both blocks are expected to be single-statement and there should be no COMMAs or other ways to modify the value (in the common case, just checking numbers doesn't mean they're the same). I think it's good as is, but I'll file a PR to clean up this phase a bit, e.g. move these rules to a sort of macros-based table
@EgorBo should we merge this? |
Fixes #78385