Open migrator opened 9 years ago
summary: Not Defined
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.
status Not Defined creator: lowas...@google.com created at: Sep 4, 2014
i'm conflicted over the fact that Function.apply is annotated as nullable, yet this causes an exception
FluentIterable
relevance: 2