https://issues.apache.org/jira/browse/GROOVY-7362 <https://issues.apache.org/jira/browse/GROOVY-7362> https://issues.apache.org/jira/browse/GROOVY-8496 <https://issues.apache.org/jira/browse/GROOVY-8496> https://issues.apache.org/jira/browse/GROOVY-8497 <https://issues.apache.org/jira/browse/GROOVY-8497>
And https://youtrack.jetbrains.com/issue/IDEA-173360 <https://youtrack.jetbrains.com/issue/IDEA-173360> which is basically GROOVY-7362. — Daniil Ovchinnikov Software Developer JetBrains jetbrains.com “Drive to develop” > On 10 Mar 2018, at 16:24, Jochen Theodorou <blackd...@gmx.org> wrote: > > On 10.03.2018 10:36, Daniil Ovchinnikov wrote: >> Thank you for looking into this. >>> In an IDE, if you have x.<auto complete keys here> you would then be >>> presented with getProperty, setProperty and get/setMetaClass. Do we >>> actually want that? >> These methods are public and non-synthetic in GroovyObject interface so they >> will be suggested independently of their implementations. > > good point. So what is actually the downside of them being synthetic right > now? > > > bye Jochen >
