<asterite>
No, because maybe between that statement and the next one another thread makes @x nil
<asterite>
At least that's our excuse for not implementing it :-P
<asterite>
But another thread can't change a local variable
<farleyknight>
Okay, I've used try a few times.. It seems the the appropriate thing here..
<bcardiff>
farleyknight might be expecting the if @x to restrict @x to be non nillable. right?
<asterite>
Yes, but that's not safe, at least not in a concurrent world
<farleyknight>
Will there ever be "locked" classes where instance variables can't be modified by outside threads?
<waj>
I think it would be fairly complicated for the compiler to deduce that
<emmanueloga>
hey asterite :)
<farleyknight>
I think the try idiom is a fair enough replacement for that bit of inference. I was just a bit confused why it worked fine for local variables but not instance variables!
<asterite>
Yes… `try` and `if var = @var` are the two alternatives that we have right now