IMO, I think they are very useful, especially since the IDE (e.g. IntelliJ
IDEA) can use them to detect problems (e.g. NPEs) earlier rather than later.
For example, *Spring* 5 just introduced 2 new annotations: @Nullable [1]
(declaring possible null parameters, returns values or fields) and
@NonNu
What's the general opinion of @NotNull annotations? Would they be useful?
On Fri, Jul 14, 2017 at 9:23 AM, John Blum wrote:
> +1 as well.
>
> However, I will caution this... use Java 8's new java.util.Optional class
> in your codebase judiciously. Using it everywhere, especially on critical
> c
+1 as well.
However, I will caution this... use Java 8's new java.util.Optional class
in your codebase judiciously. Using it everywhere, especially on critical
code paths can and most likely will affect your performance.
Internally, j.u.Optional allocates new objects for nearly every operation
(
+1
We are taking a similar approach to refactoring of the C++ client. Specifically
with refer to nullptr we are trying to eliminate it from all public APIs.
Sent from my iPhone
> On Jul 13, 2017, at 3:17 PM, Kirk Lund wrote:
>
> Please try to imagine a world of no nulls.
>
> https://www.orac
