[jira] [Resolved] (GROOVY-8501) Switch internal details of @ImmutableBase existing constructor validation

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Resolved] (GROOVY-8501) Switch internal details of @ImmutableBase existing constructor validation

JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/GROOVY-8501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul King resolved GROOVY-8501.
-------------------------------
       Resolution: Fixed
         Assignee: Paul King
    Fix Version/s: 2.5.0-rc-1

Proposed PR merged.

> Switch internal details of @ImmutableBase existing constructor validation
> -------------------------------------------------------------------------
>
>                 Key: GROOVY-8501
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8501
>             Project: Groovy
>          Issue Type: Task
>            Reporter: Paul King
>            Assignee: Paul King
>            Priority: Major
>             Fix For: 2.5.0-rc-1
>
>
> Currently @ImmutableBase validates that no existing constructors are present. It requires @ImmutableBase to appear before @TupleConstructor and @MapConstructor. It allows @Builder with the InitializerStrategy to have been processed earlier and uses some node metadata tracking to allow this to happen. If we change to instead checking for the @Generated annotation instead of node metadata, these ordering restrictions can be relaxed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)