I agree with Darrel, Bill has made some very compelling arguments.
I also add my vote of -1 to remove "noisy" final keywords from local
variables.
I am VERY interested in understanding how the JVM would handle this, as
final is a keyword that stops the reassignment of the variable with
another value. It would never stop immutability concerns. This can only
be achieved by following stricter rules regarding how Pojos are created
and coding practices.
I believe it is better to be more secure and opt-out when not required,
than trying to add-in being more secure (as you are more likely to miss
things).
--Udo
On 6/19/19 08:41, Darrel Schneider wrote:
I find Bill's argument of using final by default on everything convincing
and removing it when you have something that needs to be changed.
It is not in keeping with my current practice but I'm willing to change.
So I vote -1 to not using "final" on local variables.
On Wed, Jun 19, 2019 at 7:29 AM Anthony Baker <aba...@pivotal.io> wrote:
Just to confirm, the primary place where we make project decisions is on
the dev@geode list. Thanks!
Anthony
On Jun 19, 2019, at 7:19 AM, Bill Burcham <bburc...@pivotal.io> wrote:
I feel that a lot more
conversation is needed, outside email. On the other hand, this mailing
list
is a fine place to deliberate. But to deliberate successfully on this
issue, via email, I think we'll have to break it down further, and we'll
have to be comfortable with the process taking a long time.
