I agree that if you disable exports you can run into the same problem.
However, I would guess most GWT users would have no reason to turn it off
and in that case it would be consistent. It seems more an optimization for
a use case most people won't have.
On Tuesday, April 12, 2016 at 12:51:12
Unfortunately, that is not true. A lot of people just need to deal with
native types without any need for exporting their own types to JavaScript
and shared libraries will start accumulating unnecessary code for all of
them if it is enabled by default. We have already seen this Google.
Actually mor
(just in case someone read this thread) This problem has already been fixed
in 2.8.0-SNAPSHOT. Thanks.
On Tuesday, October 27, 2015 at 9:17:47 PM UTC+1, Ignacio Baca
Moreno-Torres wrote:
>
> At last!
> https://github.com/ibaca/gwt-instantiable-inference-bug/blob/master/src/main/java/com/bacamt/