Sorry for this crime of thought, i was thinking it was a chance to talk
about it and explore different paths.
That, this, is the only answer, well, life is hard.
Just for the records, i did stop thinking like that when i started golang,
its not like you are given the choice.
Psst ... I must ask you about the address of the shop where you bought this
wonderful magical crystal bowl you use to read in the future.
I kind of fail to find one for my current self.
thanks ;)
On Friday, June 2, 2017 at 10:17:54 AM UTC+2, Florin Pățan wrote:
>
> Since everyone thinks it but nobody bothers to reply to it: this whole
> thing you propose can be currently done with a for loop, which not only is
> explicit about what it doing, but it also lets you control if you want to
> exit early from it and so on. Complicating the whole language because
> something is cool (yet looks like a really complex thing that you need to
> think about while reading the code) is in no one's benefit. Stop trying to
> avoid a couple of extra rows of for {} (where the third row is literally
> just an "}") and start embracing the fact that you can understand the code
> by looking at it and not apply any complex mental acrobatics to figure out
> what those three lines of code are doing. Your future self/person after you
> will thank you for that.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
