News for hackers. Stuff that matters.
Re:A bit of background on compilers exploiting signed overflow by btrask on Sunday May 08, 2016 @06:49PM (#11656370)
Genuine question: what do you do when you want to implement your own loop mechanism, iterator, array type, or whatever?
Re:A bit of background on compilers exploiting signed overflow by cokernel_hacker on Sunday May 08, 2016 @07:09PM (#11656454)
It is the job of the language to ensure that language primitives are reusable and composable.

I think this would apply to whatever mechanism is designed to describe a loop's iteration space.

Re:A bit of background on compilers exploiting signed overflow by Sean1708 on Monday May 09, 2016 @10:10AM (#11659948)
Most languages use some sort of interface whereby if you implement certain methods for a type then that type can be iterated over using a for loop.