The only thing I can think of is that when the class is created for the
lambda in gwtastbuilder, the super class or implemented interfaces are not
set up correctly.
I'll check later to see if that is there case.
On Oct 24, 2015 19:07, "'Ray Cromwell' via GWT Contributors" <
google-web-toolkit-cont
Are you using @JsFunction/JsInterop? Unless the implementation has changed
recently, Lambda's are supported in GWT by essentially synthesizing static
inner classes, and so if static inner classes work, but lambda's don't,
it's really weird. The optimization stages no nothing of lambdas and only
see
This was from 94e45975a06ece1b8d65541aaabf833f9d8c7b07 (6 October 2015 at
04:29:19 GMT+2), I'll try tomorrow with HEAD, but looking the commits looks
improbable that the problem has been solved.
On Sat, Oct 24, 2015 at 10:30 PM 'Roberto Lublinerman' via GWT Contributors
wrote:
> Are you using a
Are you using a recent snapshot?
On Oct 24, 2015 04:40, "Ignacio Baca Moreno-Torres"
wrote:
> There is a bug which optimizations nullify variables which might not be
> null. I'm trying to reproduce the error outside our app but I can't, I'll
> continue trying, but for now I going to describe the
Anonymous classes works correctly in both cases.
El sáb., 24 de octubre de 2015 19:52, 'Ray Cromwell' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> escribió:
> Does it still happen if you use an anonymous inner class instead of a
> lambda?
>
> On Sat, Oct 24, 2015 at 4:
Does it still happen if you use an anonymous inner class instead of a
lambda?
On Sat, Oct 24, 2015 at 4:54 AM, Ignacio Baca Moreno-Torres <
igna...@bacamt.com> wrote:
> Other situation producing the same problem. If next code is replaced by
> lambda and method reference... the next block end up b
Other situation producing the same problem. If next code is replaced by
lambda and method reference... the next block end up being optimized as if
response is always null.
//noinspection Convert2Lambda,Anonymous2MethodRef IGP-1732 gwt optimize
incompatible
tracker.add(heads.subscribe(new Action
There is a bug which optimizations nullify variables which might not be
null. I'm trying to reproduce the error outside our app but I can't, I'll
continue trying, but for now I going to describe the problem.
return service.get().getBootstrap().bootstrap().doOnNext(data -> {
Account account =