-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Fix: string/symbol array literals recognize nested delimiters and escaped whitespace #5667
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
Merged
RX14
merged 1 commit into
crystal-lang:master
from
straight-shoota:jm/fix/percent-array-literal
Feb 2, 2018
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
loop do?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.
Everywhere else in this file it's
while true... I'd rather stick with that until (maybe) all occurances would be converted (not sure if).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.
loop doandwhile trueare the same. In fact,loop domight be a bit slower to compile, and it has a counter.Please, let's not comment such things, nowhere it says that
loop dois better thanwhile truenor that it's the std/compile style that we prefer.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.
@asterite Since
loop dois borrowed from Ruby, we could borrow the style guide rule for this too.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.
But they are not the same. That advice is wrong. If you declare a variable inside the
loop, it won't exist outside it, because of blocks. So I always preferwhile true. It's also so much lightweight: no block involves, just pure procedural code.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.
BOTH are accepted. End of discussion.
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.
Having a style guide even if it says "both are accepted" would help avoiding such discussions ;)
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.
Having no style guide and having everyone stop commenting on such small details would also help.
I mean, we have a formatter already. If it's formatted, we accept it. If there's no performance loss between two constructs, we accept both of them. That's the style guide.
Otherwise, as I said before, let's restrict the language to just the constructs we like. Let's end with a language like Go.
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.
Just a comment - the "style guide" in ruby is not official. I don't agree with most of it either. I have no comment on crystal itself, that is up to the crystal devs, but hugoabonizio referred to the style code in ruby, used and created by rubocop + the rubocop devs, and I have to add that this is not an "official" style guide. It's just the default one that the rubocop main dev added and you can change it by customizing rubocop (so I don't have a big problem with it either).
Uh oh!
There was an error while loading. Please reload this page.
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.
Hey, there is ameba, is a nice tool, have been used successfully on amber framework amberframework/amber#465 and will be probably integrated in scry crystal-lang-tools/scry#58 too 😉
Thank you @veelenga ! 🎉