GWT already not conforms to java from numerical perspective. You can easily
leak, for example, non-Integer types disguised as 'int' in the type system.
This causes all sorts of surprises for people who ends up hitting them but
quite luckily most people/apps doesn't care about it. The proposal mostly
expands it to boxed types w/ instanceof behavior which is probably even
less likely to cause issues. But regardless, we need to prove/disprove this
in practice, then we can discuss it from there.

On Fri, Nov 28, 2014 at 5:50 AM, Danilo Reinert <[email protected]>
wrote:

> What Jens put is very reasonable and I also believe that such impactful
> optimizations should be optional and documented that way.
>
> Em sexta-feira, 21 de novembro de 2014 18h48min45s UTC-3, Jens escreveu:
>
>> It could be conditioned on jsinterop being switched on or not, in
>>> general though, more and more compiler switch modes I think encourage
>>> lazy/bad code practices in the ecosystem.
>>>
>>
>> Conditioned on jsinterop would really be bad, since all js wrapper libs
>> will soon be based on jsinterop which makes that switch literally always on.
>>
>> IMHO any optimization that breaks java behavior should be optional and
>> only explicit activated by a project's dev team because the dev team needs
>> to know the implications of these optimizations.
>> GWT needs to be very careful with such optimizations as most people
>> choose GWT because they are not that familiar with JS and they expect that
>> all java behaviors carry over to JS once the app is compiled and not just
>> most of them.
>>
>> Back in the days I lost quite some time figuring out why a GWT-RPC
>> request failed to serialize and it was because browsers had started using
>> sub pixel coordinates and GWT has treated int, float, double the same which
>> caused trouble in a serializer.
>>
>> In general I am fine with such optimizations but I would prefer if all
>> such optimizations are turned off by default and there would be a chapter
>> about optimizations in the documentation which describes the implications
>> of such optimizations in more detail, especially for Java devs without lots
>> of JS background knowledge.
>>
>> -- J.
>>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA3OxLbO063Kx_9oXXBGk4PqMvm2HPLO8%3DnfWzkjAkuc%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to