The example you linked is an interesting case: clearly the author has enough Java knowledge to understand the Nullable concept, or they wouldn't have chosen to use java.util.Optional. In these cases I'm not sure they will appreciate if the analyzer is being a wise-ass by pointing out that they should use null instead. On the other hand, the goal of this exercise is to practice using null.

I think I would prefer it if we leave an actionable comment that acknowledges that using java.util.Optional is a great way to deal with nullable arguments, but nudges the author to also try to solve the exercise without it. Once #2555 is completed, we could even point out that optionals are covered in a later concept.

What do you think?

I think I would prefer it if we leave an actionable comment that acknowledges that using java.util.Optional is a great way to deal with nullable arguments, but nudges the author to also try to solve the exercise without it. Once #2555 is completed, we could even point out that optionals are covered in a later concept.

What do you think?

Sure, I like that!