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.
Yes! One decisive advantage that high-level iteration constructs have over for loops is that they're easier to optimize.
One obvious example here is bounds checks: there's no need to have infrastructure to optimize out bounds checks over arrays during loops if you have a construct that eliminates the indexing entirely.