3 ms·

Yes, thats surprising behavior. Fortunately its fixed in 1.9. :) Spoiler alert: . . . 1.8.x produces 3 while 1.9 produces :foo

• jluxenberg 16y ago
  Hmm, interesting. I suspect this will break many things, but I'm happy that they have changed it.
  • kemiller 16y ago
    The problem is not as pervasive as you might think, though it does happen.
• lincolnq 16y ago
  Why was this broken in the first place? (What abomination of semantics would cause this behaviour)?
  • gnaritas 16y ago
    Closure variables not having their own scope and shadowing method level vars. They're simply implemented as method level vars, so not true closures.
    • lincolnq 16y ago
      I got that, but I don't understand why it should gain the value 3 before a single execution of the loop.
      • mike 16y ago
        It's only at the end that the value of x is 3. The puts x immediately after x = :foo does print :foo