Mailing-List: contact dev-help@groovy.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.apache.org
Subject: Re: Groovy and Java 9
To: dev@groovy.apache.org
References: <CACZ9-KdG6WgpTTuyUuYf5K_TQQrrad5JtS8t6kDko2QJW34i9A@mail.gmail.com>
 <57454264.6040603@gmx.org> <1464160471.1712.3.camel@winder.org.uk>
From: Jochen Theodorou <blackdrag@gmx.org>
Message-ID: <5745FE8D.3020801@gmx.org>
Date: Wed, 25 May 2016 21:35:41 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <1464160471.1712.3.camel@winder.org.uk>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
archived-at: Wed, 25 May 2016 20:09:25 -0000

On 25.05.2016 09:14, Russel Winder wrote:
> It is perhaps worth pointing out that some of us have Groovy stuff
> running on JDK9 already. Now that I have a Gradle that runs on JDK9, I
> haven't yet written Groovy code that breaks on JDK9 and requires JDK8,
> but then I haven't tried to use any modules stuff.

There is ground to suspect that we won´t create callsite caching helper 
methods at runtime using JDK9 and non-indy mode. Did you maybe check 
performance under JDK9 with and without indy? I would be interested in 
knowing if you see a bigger difference compared to JDK8

bye Jochen