Re: [go-nuts] do {} for x, why or why not?

2017-03-03 Thread Ian Lance Taylor
On Fri, Mar 3, 2017 at 2:00 PM, wrote: > I rather like Go's loops, they are simple and easy to remember, and the > problem so many languages have with dozens of different loop keywords is > neatly avoided. Too many loop types is simply a pain, but I think that one > more wouldn't hurt... > > Basi

Re: [go-nuts] do {} for x, why or why not?

2017-03-03 Thread milo . christiansen
I agree that a new keyword seems like overkill, which is one reason I asked for other's ideas. I don't particularly agree that there is no need for a loop that checks its condition after instead of before, but in any case it's not a big deal. Mostly I am interesting in what others think. On Fr

[go-nuts] do {} for x, why or why not?

2017-03-03 Thread milo . christiansen
I rather like Go's loops, they are simple and easy to remember, and the problem so many languages have with dozens of different loop keywords is neatly avoided. Too many loop types is simply a pain, but I think that one more wouldn't hurt... Basically the following would be helpful in some case