News for hackers. Stuff that matters.
Re:Fixing for Loops in Go 1.22 by scottlamb on Tuesday September 19, 2023 @04:23PM (#37575984)
Others have suggested that Rob Pike and Ken Thompson have some language design experience, to state it mildly. I also want to point out...

> Russ Cox and the Go team learned that the loop variable capture semantics are flawed not by reflecting about how their language works, but through user feedback.

I think "user feedback" isn't the whole story. I've noticed in other changes (e.g. the monotonic time change [1]) they've done a pretty disciplined study of user code in Google's monorepo and on github. That's mentioned in this case too. This is a good practice, not evidence of failure.

[1] https://go.googlesource.com/proposal/+/master/design/12914-m...

Re:Fixing for Loops in Go 1.22 by kaba0 on Tuesday September 19, 2023 @05:34PM (#37577084)
> Rob Pike and Ken Thompson

They are huge names in the field, but honestly, they just suck at language design itself.

Re:Fixing for Loops in Go 1.22 by Cthulhu_ on Wednesday September 20, 2023 @06:02AM (#37582367)
Can you substantiate that or is this just flaming?
Re:Fixing for Loops in Go 1.22 by scottlamb on Wednesday September 20, 2023 @04:01PM (#37589337)
I'm sure they could come up with a list of language decisions they disagree with.

I'm equally sure that if you asked kubb, kaba0, and three other strongly opinionated folks for a list of good language designers, each of the <5 lists you get back would be very short, and there'd be no overlap between them.