JEP draft: Prepare to make final mean final
openjdk.org
JEP draft: Prepare to make final mean final
1–10 of 143 posts
Re: JEP draft: Prepare to make final mean final
#2final ly
Re: JEP draft: Prepare to make final mean final
#3Great! Now can we make `final` the default for all fields, variables, and parameters?
(yes yes, I know, that would break syntax... but please come up with something to discourage mutability)
Re: JEP draft: Prepare to make final mean final
#4From my perspective as a C++ developer, every attempt to use `const` for compiler optimization appears to be stymied by the existence of `const_cast`, because modifying a `const` value is only undefined behaviour if the underlying object is `const`. Glad to see that Java is willing to break the language to improve it.
Re: JEP draft: Prepare to make final mean final
#5So this is about warning about using deep reflection or such to modify fields marked as final.
Not a Java dev, so I thought it might be related to classes marked final somehow. But this seems like a reasonable proposal, at least in spirit.
Re: JEP draft: Prepare to make final mean final
#6A cursory glance at "setAccessible" usage reveals popular libraries such as serializers like gson and jaxb, class manipulation and generation like cglib, aspectj and even jdk.internal.reflect, testing frameworks and libraries including junit, mockito and other mocking libraries, lombok, groovy, spring, and the list goes on and on.
My bet is that this will be yet another "checked exception" or "module system", where many applications now need to add "--add-opens". If you'll use ANY of many of the more popular frameworks or libraries you'll end up giving this assurance away, which will make library developers not able to rely on it and we're back to square one.
Re: JEP draft: Prepare to make final mean final
#7Great! Now can we make `final` the default for all fields, variables, and parameters? (yes yes, I know, that would break syntax... but please come up with something to discourage mutability)
Const-ness in C++ is something I miss in other languages. Being immediate able to see that this function or method couldn't mutate the object made it so much easier to reason about the code.
Yeah I know there's ways around it, but then the author known what they told the other party to expect.
Re: JEP draft: Prepare to make final mean final
#8I don’t see a way to opt-in to a hard error if this happens somewhere in the guts of the code (third-party probably).
Re: JEP draft: Prepare to make final mean final
#9So happy to see this, thank you Ron and Alan.
Re: JEP draft: Prepare to make final mean final
#10I would like to see some realistic example scenarios where this could actually lead to a speedup and how much it actually speeds up.