You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a module-info exists and it has the Nullmarked annotation, all packages contained within should be treated as though they are also Nullmarked unless they are NullUnmarked, and etc... you get it. I know this behavior is desired, so this is mostly just so it can be tracked.
The text was updated successfully, but these errors were encountered:
xenoterracide
changed the title
Support Nullmarked on module-info
Support Nullmarked on module-info (JPMS)
Dec 6, 2024
We should and will eventually support this. But generally speaking, at this point it doesn't seem like a library can rely just on annotating module-info to get the desired behavior; see jspecify/jspecify#496 (comment)
If a module-info exists and it has the
Nullmarked
annotation, all packages contained within should be treated as though they are alsoNullmarked
unless they areNullUnmarked
, and etc... you get it. I know this behavior is desired, so this is mostly just so it can be tracked.The text was updated successfully, but these errors were encountered: