[
https://issues.apache.org/jira/browse/GROOVY-10925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17684280#comment-17684280
]
Paul King commented on GROOVY-10925:
------------------------------------
[~emilles] I think something like the above mentioned PR is the way to go. The
change to @Immutable might perhaps be best split off. Also, I wonder whether
the testPrivateFinalFieldIgnoredForMapConstructorWithoutIncludeFields behavior
is what folks would expect or rather an error.
> @TupleConstructor namedVariant breaks on setting private final fields in
> constructor
> ------------------------------------------------------------------------------------
>
> Key: GROOVY-10925
> URL: https://issues.apache.org/jira/browse/GROOVY-10925
> Project: Groovy
> Issue Type: Bug
> Affects Versions: 4.0.8
> Reporter: Joe Li
> Priority: Major
>
> @TupleConstructor `namedVariant` Breaks in Groovy4 when setting values to
> private final fields in constructor
>
> Example code in Groovy4 that throws the `Unrecognized namedArgKey: x` error:
> {code:java}
> import groovy.transform.*
> @TupleConstructor(includeFields = true, namedVariant = true)
> @ToString(includeNames = true, includeFields = true)
> class Foo {
> private final int x = 1
> private int y = 2
> private final int z
> }
> println new Foo(x:3, y: 3, z: 3) {code}
>
>
> After removing the `namedVariant` and add the `@MapConstructor` the code
> works:
> {code:java}
> import groovy.transform.*
> @MapConstructor(includeFields = true)
> @TupleConstructor(includeFields = true)
> @ToString(includeNames = true, includeFields = true)
> class Foo {
> private final int x = 1
> private int y = 2
> private final int z
> }
> println new Foo(x:3, y: 3, z: 3) {code}
>
>
> Related issue:
> [GROOVY-10919|https://issues.apache.org/jira/browse/GROOVY-10919],
> @MapConstructor Breaks in Groovy4 when combined with @TupleConstructor, fine
> in Groovy3
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
