>
> 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 w
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.
Better would be a "lint"/"checked mode" that throws hard errors in
your app when you do something that violates the assu
The one of the problems is the boxing makes the support of method
overloading, var args, etc. more complicated and much slower in JsInterop.
Making it optional is not going to help with those.
I think with the experiment we will have a very good data on the impact of
this change, after that we can
Can that be an option ? So that the user knows what happens consciously, in
order to optimize the runtime. I admit, that this would not simplify the
jscompiler base code, but would provide the user with another powerful
optimization...
Just an idea...
Thanks
Arnaud
Le vendredi 21 novembre 2014
