[
https://issues.apache.org/jira/browse/GROOVY-8300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143170#comment-16143170
]
mg commented on GROOVY-8300:
----------------------------
I think method visibility does not need to be taken into consideration because:
# Imho either one wants to be sure parameters cannot be changed by accident -
or not, and I do not see how this could depend on whether a method is e.g.
private or public
# But more importantly: I feel auto applying the final keyword to parameters
under certain circumstances only would be confusing in practice, so I would
argue against it.
> Groovy should have an @AutoFinal annotation
> -------------------------------------------
>
> Key: GROOVY-8300
> URL: https://issues.apache.org/jira/browse/GROOVY-8300
> Project: Groovy
> Issue Type: New Feature
> Reporter: Paul King
>
> When defined on a method or constructor, all parameters of that
> method/constructor will be final. When applied on a class, the annotation
> applies to all methods/constructors.
> Still to be determined:
> # Should visibility matter, e.g. would it apply to all public, protected,
> private, etc. members, or does there need to be some ability to customise?
> # Should the annotation apply to fields/properties? Applying 'final' to a
> field/property seems to be more efficient than applying @AutoFinal but would
> there ever be a desire to apply such an annotation to all fields/properties?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
