-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Prevent NameSimplifier and VarNameCleaner from producing Yul identifiers with leading and trailing dots #15149
Prevent NameSimplifier and VarNameCleaner from producing Yul identifiers with leading and trailing dots #15149
Conversation
test/cmdlineTests/yul_leading_or_trailing_dot_in_name/input.yul
Outdated
Show resolved
Hide resolved
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.
Also some general remarks:
- The PR is missing a changelog entry.
- When a PR fixes everything in the original issue you should use the github feature that will fix the issue automatically when the PR is merged. I.e. just add
Fixes #11496
in the PR description. - I saw that the issue was moved to the 'In progress' column on the triage board. That column actually means that triage is progress :) It was added so that multiple people don't waste time triaging the same issue at the same time. The issues are only really meant to spent a short time there - triage never really takes all that long.
test/cmdlineTests/yul_leading_or_trailing_dot_in_name/input.yul
Outdated
Show resolved
Hide resolved
test/cmdlineTests/yul_leading_or_trailing_dot_in_name/input.yul
Outdated
Show resolved
Hide resolved
Just noticed that you do have this but it's in the commit message. I'd recommend against it since this adds a lot of noise to the issue you mention this way - the commit appears there again and again each time you rebase the branch. It works much better when used in the PR instead. |
f96d849
to
d4c4b06
Compare
Ahh I have misunderstood the "in progress" :) thanks for pointing that out! |
d5aadd0
to
947198b
Compare
6c97388
to
7f89de1
Compare
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.
If it passes CI, it's good to go.
7f89de1
to
bbd5e2e
Compare
Whelp, forgot to update the test outcome after updating indentations, care to re-approve @cameel ?:) |
Fix changelog entry for #15149
Fixes #11496