-
-
Notifications
You must be signed in to change notification settings - Fork 518
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
for...in loop nitpicks #92
Comments
So how would you suggest changing the wording? It may be able to be improved. I would say that most do not use it because they aren't solving problems where the last iterated value is not needed to be kept. Or because of the same reason that people don't tend to use 'or' and 'and' as opposed to I have noticed that as people become more experienced with Ruby they start to use each of these things as intended and where appropriate, because they do see the features and nuances given by each. And though it can be the source of some weird bugs, I don't think it is the cause of those bugs. The cause is simply not keeping track of your variables. |
ah yes i forgot to put my suggestion! Perhaps pointing out the behavior of
would suffice. I suppose another good way is to make a concrete example. i.e.
vs.
I argue the reason we don't use |
This is a really great distinction. The comment lives here: https://github.com/exercism/rikki/blob/master/comments/ruby/for_loop/for_loop.md Do you want to take a stab at improving it? |
ah you found my kryptonite: English! haha I'll take a stab sometime today, thanks for the link =) |
LOL, I'm happy to tweak once you've given it a first pass :) |
Closing, address in: exercism/DEPRECATED.rikki#8 |
Yepp, thanks! Also: deployed. |
Correct regular answer.
Not sure if this is the right place to make this issue but I'm see a lot of automated nitpicks with:
Which isn't a 100% true, there is a reason why most don't use
for...in
and it's because it does not create a closure. i.e.Which can cause some weird bugs.
The text was updated successfully, but these errors were encountered: