[ https://issues.apache.org/jira/browse/CALCITE-4787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17418748#comment-17418748 ]
Julian Hyde commented on CALCITE-4787: -------------------------------------- The initial PR is just a proof-of-concept. It seems that the real PR will touch hundreds of files, and also require dependent projects (who have written their own rules) to make changes. So this will be a very breaking change. > Evaluate use of Immutables instead of ImmutableBeans > ---------------------------------------------------- > > Key: CALCITE-4787 > URL: https://issues.apache.org/jira/browse/CALCITE-4787 > Project: Calcite > Issue Type: Improvement > Reporter: Jacques Nadeau > Assignee: Jacques Nadeau > Priority: Major > Labels: pull-request-available > Time Spent: 1h 50m > Remaining Estimate: 0h > > In the creation of CALCITE-3328, [Immutables|https://immutables.github.io/] > was discussed as an alternative to a custom implementation. This ticket is to > evaluate the impact to the codebase of changing. Ideally, introduction of > immutables would both add flexibility and reduce the amount of code > associated with these classes. > Immutables works via annotation processor which means that it is should be > relatively seamless to build systems and IDEs. > The switch would also make it easier to work with these objects types in the > context of aot compilation tools like GraalVM. -- This message was sent by Atlassian Jira (v8.3.4#803005)