private Fields which should not be reassigned, but cannot be marked with final keyword about error-prone HOT 3 CLOSED

Original comment posted by [email protected] on 2013-02-11 at 09:41 PM

Would this be problematic for non-reflection-based DI frameworks like Dagger? They generate code which would then be compiled by javac, and if we add a check that fields with a certain annotation should be treated as final, then the generated code would also have to abide by that rule.

Labels: -Priority-Medium, Priority-Low

from error-prone.

Original comment posted by [email protected] on 2013-02-11 at 10:31 PM

I don't see a problem wrt Guice -- just use constructor injection.

I don't really like the idea of a "think of this like it's final" annotation, because you won't get the actual memory visibility semantics at runtime.

from error-prone.

Original comment posted by [email protected] on 2014-03-04 at 12:35 AM

I agree with Kevin that this is probably not a high enough priority to get done. Marking WillNotFix, but if you want to work on it please reopen and send us your code.

Status: WontFix

from error-prone.