-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Require space, semicolon, or newline after class/module/etc. header #13375
base: master
Are you sure you want to change the base?
Conversation
This probably won't have a huge impact on performance but it helps make the intent here clearer.
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.
Have you considered extracting skip_space
out of parse_path
/parse_generic
? Most calls to these methods are already followed by an explicit call to skip_space
. So maybe we could do this everywhere and reduce some complexity?
This is just an idea. I haven't actually tried it and maybe it won't work well. It's not a requirement for merging.
# Conflicts: # spec/compiler/parser/parser_spec.cr
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.
I noticed another minor thing.
Again, it's not a requirement, but I think it would improve code quality a bit.
We should add specs with the expected valid cases in order to not run again with the same issue that forced the reverting of #11209. |
Originally included in #11854
Closes #11209
Unrelated, a lot of tests in
describe "end locations" do ... end
don't have anything to do with, well, end locations.