I'd vote for only supporting zone offsets at first.
--
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
> Is it acceptable that an official GWT implementation of the time API would
> be based on moment.js ? Or is it expected that it is all implemented with
> standard browser API and pure Java code ?
>
Because GWT compiler can not see/optimize external JS files, an official
GWT implementation
Is it acceptable that an official GWT implementation of the time API would be
based on moment.js ? Or is it expected that it is all implemented with standard
browser API and pure Java code ?
On 5 Dec 2018, 15:03 +0100, Jens , wrote:
>
> > For the emulation changes I can live with what is
> For the emulation changes I can live with what is available now and get
> some more in a later release. But how does the gwt team decide which are
> crucial and which ones can be done in a separate library ? The java.time
> API should really be considered, the Date object has been
I am using var in some simple cases and the gwt compiler did not have a
problem. I don’t use them on lambda parameters though. So my code is using
Java 10 but not 11 features.
For the emulation changes I can live with what is available now and get some
more in a later release. But how does
I think the JDT version GWT currently uses does not officially support Java
11. However Java 11 has no notable syntax changes except the var keyword
for lambda parameters. So it might work, but maybe it doesn't. Have you
tried running GWT with Java 11 and using that new syntax?
Also no Java
