Again, where does this mutation occur? The spec shouldn't allow any such thing to begin with; it should mandate exactly what my compiler does: as soon as .next returns, copy .value into the loop variable. The developer shouldn't have any access to the return value from within the loop at all; if he does, that should (ideally) be considered a violation of the standard.
On Sun, Feb 15, 2015 at 8:09 AM, Kevin Smith <[email protected]> wrote: > When I can get more sound abstractions for no additional cost (eventually) >> I'd rather not introduce implicit mutable state into the application. >> Developers won't be aware of it being mutating and the whole notion of a >> mutating-at-a-later-point return value is very error-prone in my opinion. >> > > Right. Mutating the returned object isn't really tenable from a usability > point of view. > > > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
