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
Unfortunately, the current nullability annotations don't work in all the places where they are needed for strict null-marking. For instance, we currently can't correctly mark the generic value type of the Attribute Map Entry as nullable with javax.annotations.Nullable:
public class Attribute implements Map.Entry<String, @Nullable String>, Cloneable {
Would you mind if I'd create a PR to switch the project to strict nullability using Jspecify? This would also allow us to switch the two internal "NonNullByDefault" annotations over to @NullMarked.
Stefan
The text was updated successfully, but these errors were encountered:
Hi - sure I'd be happy to take a look at a PR and improve this. I'm not very familiar with jspecify so will I will need to dig into that. Impl needs to maintain API compatibility.
Away from jsr305
With the goal of having a nullability assertion annotation that supports Java modules, so we can release the next version of jsoup.
Annotation options appear limited and does not support @WillClose, but rest appears OK.
Will fix#2028, #1992
Away from jsr305
With the goal of having a nullability assertion annotation that supports Java modules, so we can release the next version of jsoup.
Annotation options appear limited and does not support @WillClose, but rest appears OK.
Fixes#2028Fixes#1992
Hi,
Unfortunately, the current nullability annotations don't work in all the places where they are needed for strict null-marking. For instance, we currently can't correctly mark the generic value type of the Attribute Map Entry as nullable with javax.annotations.Nullable:
Would you mind if I'd create a PR to switch the project to strict nullability using Jspecify? This would also allow us to switch the two internal "NonNullByDefault" annotations over to @NullMarked.
Stefan
The text was updated successfully, but these errors were encountered: