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 2016/12/02 20:52:58 UTC

[jira] [Created] (GROOVY-8016) @TupleConstructor could use the order of properties listed in 'includes' when that option is used

Paul King created GROOVY-8016:
---------------------------------

             Summary: @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


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.4#6332)