Paul King resolved GROOVY-7601.
    Resolution: Won't Fix

Less of an issue than before and should be recast in terms of current 
functionality if a similar feature is still desired. But thanks for the 

> shallow parameter for @Immutable
> --------------------------------
>                 Key: GROOVY-7601
>                 URL: https://issues.apache.org/jira/browse/GROOVY-7601
>             Project: Groovy
>          Issue Type: Improvement
>    Affects Versions: 2.4.4
>            Reporter: Christopher Smith
>            Priority: Major
> I am using {{@Immutable}} for some command objects, where some of the fields 
> are sometimes-complex domain objects. In this case, I don't need deep 
> immutability for semantic correctness, and it would be helpful to have a 
> parameter to indicate that the transform shouldn't bother checking the 
> fields' types, just make them final and generate the appropriate methods:
> {code}
> @Immutable(shallow = true)
> class PayCommand {
>   Invoice invoice
>   Money amount
> }
> {code}

This message was sent by Atlassian JIRA

Reply via email to