Closed GoogleCodeExporter closed 9 years ago
I think we take the position that a parameter has to be @Nullable if *any*
implementation of the type permits nulls there. This is certainly not ideal.
(It's also not ideal that I'm not 100% sure that I have our policy right.) For
general despair around the issue of nullability annotations, see issue 1812.
For this specific case, we can be more optimistic. We can improve the error
message and the doc. I'm modifying this bug's title to focus on that.
Original comment by cpov...@google.com
on 18 Sep 2014 at 10:00
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
legrand....@gmail.com
on 15 Sep 2014 at 7:21