I commonly generate custom runtime exceptions for situations like this, but
it perhaps would be nice to have the compiler flag where this situation is
likely to happen too.
Perhaps it is a feature of a later release...
On Fri, 25 Jun 2021 at 15:30, Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:
> Yes, googled a bit for this, doubt it exists as a feature in JDK 16.
>
> Gj
>
> On Fri, 25 Jun 2021 at 07:23, Lars Bruun-Hansen <lbruunhan...@gmail.com>
> wrote:
>
>> What @Nonnull in Java ? Have I missed some news about a new feature
>> in the JDK?
>> Various third party libraries implement some form of non-null
>> annotation and you will have to use one such library ... unless I
>> missed some new JDK feature. :-)
>>
>>
>>
>> /Lars
>>
>>
>>
>>
>>
>> On Fri, Jun 25, 2021 at 5:40 AM Owen Thomas <owen.paul.tho...@gmail.com>
>> wrote:
>> >
>> > Ok, thanks Geertjan. Let me know what you find.
>> >
>> > On Fri, 25 Jun 2021 at 12:59, Geertjan Wielenga <
>> geertjan.wiele...@googlemail.com> wrote:
>> >>
>> >>
>> >> Maybe it doesn’t support it yet. Will try to find out.
>> >>
>> >> Gj
>> >>
>> >> On Fri, 25 Jun 2021 at 04:39, Owen Thomas <owen.paul.tho...@gmail.com>
>> wrote:
>> >>>
>> >>> I'm using NB 12.4 with JDK 16 and I have been reading a bit of the
>> annotations article from the newest Java Magazine. I thought I'd fiddle
>> with the @Nonnull annotation, so I put one in a method's declaration where
>> I thought it needed to go so I could indicate that a parameter needed a
>> non-null value:
>> >>>
>> >>> protected boolean checkEqual(@Nonnull SU subscription){
>> >>>
>> >>> Netbeans complains that it cannot find the symbol @Nonnull, and it
>> does not give me the option to add an import.
>> >>>
>> >>> Why does this happen?
>>
>
