Closed GoogleCodeExporter closed 9 years ago
The intention of the @Nullable annotations on Function.apply is that
implementations of Function may or may not choose to accept or return null, and
to make that freedom explicit. Interpretations of @Nullable vary, however.
The behavior itself looks WAI for FluentIterable.transformAndConcat, though I'm
not sure if we should change the documentation to make this more explicit.
Original comment by lowas...@google.com
on 4 Sep 2014 at 6:47
This issue has been migrated to GitHub.
It can be found at https://github.com/google/guava/issues/<issue id>
Original comment by cgdecker@google.com
on 1 Nov 2014 at 4:08
Original comment by cgdecker@google.com
on 1 Nov 2014 at 4:17
Original comment by cgdecker@google.com
on 3 Nov 2014 at 9:07
Original issue reported on code.google.com by
rob.maxw...@gmail.com
on 4 Sep 2014 at 6:42