On Wed, Mar 25, 2015 at 11:33 AM, Colin Alworth <[email protected]> wrote:
> The trick seems to be that it is not going to be possible to add Java8 > emul code without actually using Java8 - while lambdas can be avoided, > defender methods cannot. If you need to provide a new interface like > Consumer, the supersource *must* have the `default` method(s), or it won't > actually be Consumer. > > If it were just those types, it would be possible to move them into their > own module so developers would need to inherit's the Java8 module to get > access to them, but the Collection interface itself needs to be changed to > add `default Stream<E> stream()`, plus the implementation, or else all > implementors of Collection (and Set and List) need to have an > implementation added. Even then, Stream would need to be emulated, which > references Consumer, so we can't have it be a separate module... > > ...or am I over-complicating matters? > Well, certainly there are things which will require further support in GWT and in the build, but things like adding j.u.Optional can be done without that. -- John A. Tamplin -- 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/CAM5k6X_k%2BwvoH_a_YquYcxY-uzbL%3DdANNn5eGZZJUombafbKBA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
