I see I am not the only one. Felt a bit lonely.
As for the proposals: every proposal which ‘switches’ the positions of the assignments (for x, i return i,x) will probably cause confusion. We might get used to it, but imho it looks like code smell. And for a convenience function that is extra damaging.
As for not breaking code: do we have a topic of ‘things we would do differently if we could?’ somewhere? Just to set an upper limit, keep track and not become ’Javascript’. This might seem like a joke, but it’s not. There are examples out there which show us what the results are for ‘never break’ and ‘just break it for the better’. And when we take those examples; I favor to break once in a long while. Somewhere between ECMA and Angular 
Elixir is young, let it have it’s puberty. Break once and be glad you don’t have to explain the weaker syntax the next 50 years.
Kind regards,
someone who went a long way for backwards compatibility once and learned the hard way it catches up with you.
).
