News for hackers. Stuff that matters.
Re:Rust and Go by kibwen on Monday November 10, 2014 @12:26PM (#8584837)

  > Go does help prevent errors in untested context-free code 
  > snippets... by being really really simple, and not trying 
  > to mash a ton of logic into a single line for no reason.
But there is an example in this very thread of a manually-implemented map-via-a-for-loop from a well-meaning Go user that accidentally underflows into an infinite loop.

This isn't an attack on Go (which I respect as a language for having the temerity to be opinionated, a facet that more languages need to emulate), merely bafflement at your claim that implementing everything anew via bespoke loops is somehow effective at reducing errors.

Re:Rust and Go by NateDad on Monday November 10, 2014 @05:56PM (#8587184)
Yes and that was a carefully constructed example explicitly to show problems with loops.... But underflows in loops are just not a common occurrence, which is why the example works in the first place.
Re:Rust and Go by pcwalton on Tuesday November 11, 2014 @01:31AM (#8588589)
> Yes and that was a carefully constructed example explicitly to show problems with loops

No, it was an example from my experience and a bug I have had to fix multiple times, as I mentioned. I didn't make it up.

Re:Rust and Go by NateDad on Tuesday November 11, 2014 @06:49AM (#8589374)
Sorry, yes you mentioned that. Anyway, this is a stupid thing to argue about and I apologize for my part in it.
Re:Rust and Go by kibwen on Monday November 10, 2014 @07:57PM (#8587651)
Likewise, forgetting a `.collect()` call in Rust code doesn't happen, because the compiler will tell you without fail when it's given an iterator but expects an array.