You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Paul King (JIRA)" <ji...@apache.org> on 2017/08/28 04:58:00 UTC
[jira] [Comment Edited] (GROOVY-8300) Groovy should have an
@AutoFinal annotation
[ https://issues.apache.org/jira/browse/GROOVY-8300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143369#comment-16143369 ]
Paul King edited comment on GROOVY-8300 at 8/28/17 4:57 AM:
------------------------------------------------------------
I tend to agree with your comments - though I am inclined to just leave the name as is. I'll update the description.
was (Author: paulk):
I tend to agree with your comments. I'll update the description.
> 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)