I think the only real problem here is the lack of do {} while <cond> and
even this is not a big problem. I think we can happily live with the
solution pointed by Sokolov, which is the one I use when needed. But
looking at this thread what pops up is that the lacking of this construct
at the language level opens the way to make people write the same thing in
many different ways. So, my point is that we have 3 options: 1) change the
language spec (in this case my vote should be for {} <cond>); 2) use the
Sokolov construct (in this case I suggest to include this pattern in the
language documentation to stimulate standardization); and 3) do nothing
about it (which is what is being done until now).
Just my 2 cents..
Best regards
Em quinta-feira, 3 de maio de 2018 02:45:07 UTC-3, Sokolov Yura escreveu:
>
>
> for {
> Body()
> if !Condition() {
> break
> }
> }
>
> It is thats simple, guys.
>
--
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.
