-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
empty curly have no spaces around #1234
Conversation
a3b34d6
to
9d076fc
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.
Thanks. This is a good start. Just one case remains to be covered.
while (TRUE) { } | ||
|
||
while (TRUE) | ||
{ } |
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 also need to get rid of line-breaks, if present (cf. #1232):
"while (TRUE) {
}" -> code
styler::style_text(code)
#> while (TRUE) {
#>
#> }
Created on 2024-10-06 with reprex v2.1.1
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.
Right…
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.
Ok, but that seems to imply that we always remove the line breaks inside an empy {}
, which breaks a bunch of other test cases, see e1455c6... Do you think that's inline with the style guide?
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.
Yes, I think this is what the style guide dictates, and all the new changes look desirable as per the style guide.
This is how benchmark results would change (along with a 95% confidence interval in relative change) if 9d076fc is merged into main:
Further explanation regarding interpretation and methodology can be found in the documentation. |
This is how benchmark results would change (along with a 95% confidence interval in relative change) if e1455c6 is merged into main:
Further explanation regarding interpretation and methodology can be found in the documentation. |
Thanks for the review. 🎉 |
Towards #1231.