groovy-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul King (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (GROOVY-8016) @TupleConstructor could use the order of properties listed in 'includes' when that option is used
Date Tue, 02 May 2017 02:04:17 GMT

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

Paul King closed GROOVY-8016.
-----------------------------

> @TupleConstructor could use the order of properties listed in 'includes' when that option
is used
> -------------------------------------------------------------------------------------------------
>
>                 Key: GROOVY-8016
>                 URL: https://issues.apache.org/jira/browse/GROOVY-8016
>             Project: Groovy
>          Issue Type: Bug
>            Reporter: Paul King
>            Assignee: Paul King
>              Labels: breaking
>             Fix For: 2.5.0-alpha-1
>
>
> Different JVMs return the available fields/properties in slightly different orders, so
having this option is in some ways required to achieve consistent behavior across all platforms.
This would be a minor breaking change for people using 'includes' but relying on the platform
returned order but people in that situation are facing the platform issue in any case.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message