groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cédric Champeau <cedric.champ...@gmail.com>
Subject Re: About the Phoenix plan for Groovy
Date Sun, 08 Apr 2018 18:46:20 GMT
2018-04-08 19:31 GMT+02:00 Daniel.Sun <sunlan@apache.org>:

> Hi Cédric,
>
>        At first we all admit your effort on STC is great :-)
>
>        I usually try to use STC for better performance, but sadly I have to
> turn to dynamic mode sometimes. Recently I wrote a hadoop example in Java,
> then copied the Java code as Groovy code and tried to compile with STC,
> failed to compile because of generics issue. So I believe STC had been
> tested for many scenario as you said, but it had not been tested with the
> code in some real projects, e.g. Spring, Hibernate, etc. The Phoenix plan
> tries to find a way to polish the STC and not to re-invent the wheels.
>

It was tested on real code too, I can assure you :)

>
>        Finally we wish you could set aside some time to fix some existing
> bugs, some of which are hard for us to fix but may be not that hard for you
> - the creator of STC ;-)
>

Honestly I don't have much time to work on Groovy. And if I had, the
generics STC bugs would be the last thing I'd like to get my hands into.
The ClassNode infrastructure was retrofitted to introduce generics back in
1.5, but since it was for dynamic world, it wasn't really designed for what
we do now. So, every bugfix you make is likely to introduce another bug
somewhere else. That makes the process very painful. More so when type
inference enters the game. Jochen and I spent a lot of time writing,
rewriting helper methods to make this easier, but it's just too hard for
the little time I can afford.

off topic: why is incubator always in CC of the emails you write? Looks
like your email client is misconfigured somehow.

Mime
View raw message