-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Some VN refactoring #61034
Some VN refactoring #61034
Conversation
Tagging subscribers to this area: @JulieLeeMSFT Issue DetailsIn my VN work, I've always found myself making small changes that improve the code in some minor way. Because the substantive changes to come must be focused solely on the functional parts, I've collected all the refactoring pieces in this PR. No diffs for this change per SPMI, as expected.
|
It was unused and all the callers passed the current block anyway. Also some renaming to make Assign and AssignTypeCoerce methods consistent.
By naming parameters properly.
By naming parameters properly.
In my upcoming substantive changes to this code the unreasonable level of nesting started to significantly degrade the readability of code. So, move it out of the main numbering function. The result is still pretty huge and could be split up further, but this will do for now.
Make it use a loop instead of recursion. Rename parameters to match the "Assign" variants. Add standard header comments.
19da386
to
cc7838d
Compare
@dotnet/jit-contrib |
@jakobbotsch PTAL. |
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.
LGTM. Thanks!
In my VN work, I've always found myself making small changes that improve the code in some minor way. Because the substantive changes to come must be focused solely on the functional parts, I've collected all the refactoring pieces in this PR.
No diffs for this change per SPMI, as expected.
Part of #58312.