Make lookup API context extend nullable Object

[deirn]

@NullMarked makes the lookup context C non-nullable by default.
This is not ideal since C comes from the usage of the API and thus should allow for null if needed.
For example, the transfer API has a nullable Direction context for sided storages.

Before

After

No warnings here. Note that I needed to invalidate the cache and reload the project for the warning to go away, classic IntelliJank.

[Toffikk]

why not just mark the context as nullable? it would be much cleaner if possible

[deirn]

Then it will always nullable. You want C to control it.

[cputnam-a11y]

why not just mark the context as nullable? it would be much cleaner if possible

Yeah, I would do this, marking the context as potentially Nullable like C extends @Nullable Object as jspecify recommends

[deirn]

That a thing? TIL. I'll take a look later then.
I also looked on @UnknownNullability from JetBrains annotation, but you can't use it on the type parameter.

[deirn]

Extending nullable Object seems to be working.