"Indy by default" doesn't mean anything. It's either "get rid of old call site caching/only keep indy" or, "keep as is".
Last time we tentatively started a discussion on what should be in Groovy 3 or not, we talked about upgrading to Java 8 minimally. If this happens, then we can use indy only and get rid of the "old" call site caching. But I also mentioned back then that we MUST perform benchmarks to make sure the performance of this version is as good as the previous one. Especially, I recall there were performance regressions in some areas (primitive handling, for example). Also, bumping to Java 8 only may be an issue for some. At least, it would prevent Gradle from upgrading to Groovy 3. Which may, or may not be an issue. 2017-05-29 8:20 GMT+02:00 Mario Garcia <mario.g...@gmail.com>: > +1 Indy by default > > Cheers > Mario > > 2017-05-28 14:43 GMT+02:00 Jennifer Strater <jenn.stra...@gmail.com>: > >> +1 >> >> Regards, >> Jenn >> >> On Sun, May 28, 2017 at 2:22 PM, Daniel Sun <realblue...@hotmail.com> >> wrote: >> >>> +1 for setting indy by default. >>> >>> Cheers, >>> Daniel.Sun >>> >>> >>> >>> -- >>> View this message in context: http://groovy.329449.n5.nabble >>> .com/Indy-vs-default-build-tp5741393p5741394.html >>> Sent from the Groovy Dev mailing list archive at Nabble.com. >>> >> >> >
