typetools / typetools/checker-framework
Unsoundness in Nullness Checker with record patterns
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 440
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 134
Description
Test:
import org.checkerframework.checker.nullness.qual.Nullable;
public class Test {
sealed interface IntOrBool {}
public record WrappedInt(Integer a) implements IntOrBool {}
public record WrappedBoolean(@Nullable Boolean b) implements IntOrBool {}
public static void test(IntOrBool i) {
switch (i) {
case WrappedInt(Integer x) -> {
}
case WrappedBoolean(Boolean y) -> {
y.hashCode();
}
}
}
public static void main(String[] args) {
test(new WrappedBoolean(null));
}
}
We get an NPE at runtime but it's not detected by the nullness checker. If we write case WrappedBoolean(@Nullable Boolean y) an error is reported as expected. Record patterns were finalized in Java 21; not sure if that version is officially supported by the Checker Framework yet.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the supplied Java reproducer and the nullness checker’s handling of record patterns, focusing on why the unannotated Boolean pattern variable is treated as non-null. Compare it with the explicit @Nullable pattern case and verify behavior with Java 21 record patterns. Done means the checker reports the possible null dereference in y.hashCode().
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100