[ https://issues.apache.org/jira/browse/GROOVY-11229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17806491#comment-17806491 ]
Eric Milles commented on GROOVY-11229: -------------------------------------- I still think this should be chunked up into smaller deliverables, starting with the Java 16 {{instanceof}} additions. There is much to debate in terms of usefulness in a groovy source. You state that "o instanceof Point(int x, int y) p" has "p" above-and-beyond what java provides. But why? In dynamic groovy code, "o" gives you everything "p" would. And in type-checked groovy, "o" should be inferred as "Point", so again no need for "p". Only if "o" is not a variable expression would you gain anything. So why add something that is of low to no value? I think it should be discussed before making so many changes to the AST, parser, scopes and visitors. > Support pattern matching and destructure > ---------------------------------------- > > Key: GROOVY-11229 > URL: https://issues.apache.org/jira/browse/GROOVY-11229 > Project: Groovy > Issue Type: New Feature > Reporter: Daniel Sun > Priority: Major > > See also: > [https://openjdk.org/jeps/394] > [https://openjdk.java.net/jeps/440] > [https://openjdk.org/jeps/441] -- This message was sent by Atlassian Jira (v8.20.10#820010)