3 ms·
That seems like it would be a trivial thing to do in an early compilation step... why is the workaround necessary?
by Groxx 16y ago
That seems like it would be a trivial thing to do in an early compilation step... why is the workaround necessary?
- masklinn 16y ago1. properties mean field invocations are not referentially transparent (you can only mitigate this by removing properties, or having referential transparency as part of the type) 2. multithreading means the value of the field can change from under you between the check and the access (you can solve this by eliminating threads or by transactioning your accesses)
- sirclueless 16y agoI'm pretty sure point 2 is incorrect. The compiler doesn't worry about multithreaded access to properties/variables when optimizing. You're right that such access can cause problems though. If you do want the compiler to worry about multithreaded access when it compiles, you can use the `volatile` keyword.
- masklinn 16y ago> I'm pretty sure point 2 is incorrect. The compiler doesn't worry about multithreaded access to properties/variables when optimizing. This is not about optimizing, it's about static verifications. And that's very much the point: you can't statically verify this piece of knowledge if the code can be used in a multithreaded context.
- ssp 16y agoThe problem is that if the code looks like this: if (object.some_field != null) { some_unrelated_call(); object.some_field.foo(); } proving that some_unrelated_call() didn't set object.some_field to null is very difficult.
- kenjackson 16y agoIn general, it's also difficult to prove that 'object' doesn't get set to null too.
- ssp 16y agoDepends on what you mean by "general", I suppose, but if 'object' is a local variable in a Java-ish language, then there is a fairly straightforward data flow analysis that can do a good conservative estimate.
- kenjackson 16y agobut if 'object' is a local variable in a Java-ish language, then there is a fairly straightforward data flow analysis that can do a good But if it's not, and/or if it can be adress taken...