I am curious, what does JDK 9 change to affect indy? As for switching purely to indy, I've heard a lot of issues on this list where people say it's slower, or at least the same. Has that changed now? It's on my long list to benchmark our application with indy groovy but as we use compile static almost exclusively so it’s not a high priority, but we use dynamic exclusively when producing or consuming web services where it's nice to use things like XmlSlurper that don't work with compile static and so indy is still of interest in our project.
Jason -----Original Message----- From: Jochen Theodorou [mailto:blackd...@gmx.org] Sent: Thursday, June 23, 2016 2:49 AM To: users@groovy.apache.org Subject: Re: Is it possible to enable CompileStatic for an entire project On 23.06.2016 08:00, Thibault Kruse wrote: > On Tue, Jun 21, 2016 at 6:44 PM, Cédric Champeau > <cedric.champ...@gmail.com> wrote: >> A strong -1 for both options. We already have 2 variants of Groovy >> today, indy and non indy, and in practice *nobody uses the >> invokedynamic version* because it's impractical to use. ... >> Adding a new dimension, which is orthogonal to invokedynamic makes it even >> more complicated. > > How about dropping the indy version then, and instead offer a > statically compiled one? actually, in the light of JDK9 we may drop the non-indy version.... unless we are happy with the callsite caching being purely reflection based bye Jochen ---------------------------------------------------------------------- This email message and any attachments are for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message and any attachments.
