On Tuesday, 4 September 2012 at 21:41:58 UTC, bearophile wrote:
Jonathan M Davis:
Once scope is properly enforced, then optimizing based on it
would be great, but until it is, it's a _bad_ idea.
Today we use "in" often for function arguments, and it implies
"scope". Surely some of those programs use the arguments
wrongly, this means they probably sometime escape. So are those
programs someday going to become compilation errors?
Yep.
Such things need to be implemented early in a language.
Yep.
It's very unfortunate because it puts us in a lose-lose
situations where we can't fix the language without breaking
people's code. I think the best course of action is to fix these
things as soon as possible and get the problem out of the way.
