typetools / typetools/checker-framework
WPI for nullness fails to annotate a multi-field declaration
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 440
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 134
Description
Input:
class NoExplicitInitMultiField {
// :: warning: (initialization.field.uninitialized)
Object f, g;
}
WPI for the Nullness Checker does not infer a @MonotonicNonNull or @Nullable annotation for the declaration.
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 by running the Nullness Checker with WPI on the provided NoExplicitInitMultiField example and confirm the initialization.field.uninitialized warning. Trace the WPI handling of a declaration containing both f and g, then verify that the declaration receives @MonotonicNonNull or @Nullable and that the example behaves as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100