On 5/9/16, 1:22 PM, "Josh Tynjala" <joshtynj...@gmail.com> wrote:
>That's a good call, Andy. You're absolutely right that a for-each loop >could also have its own return statements that are meant for the >surrounding function. With that in mind, I don't think there's a special >case here that the compiler can easily detect to optimize. Hmm, maybe I'm missing something. I'm not a compiler expert, but I've heard about things like "code-flow analysis" and similar techniques that I thought could be used for determining that there aren't planned exits from a loop. -Alex