typetools / typetools/checker-framework
Enable the Primitives Lock Checker test once GuardedByName is implemented
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 440
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 134
Description
Once a @GuardedByName annotation that can guard primitive types is implemented, re-enable the Primitives test in the Lock Checker test suite.
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
Locate the GuardedByName annotation and the disabled Primitives test in the Lock Checker test suite. First determine whether primitive guarding support is implemented, then re-enable the test and run the Lock Checker tests. Done means the Primitives test is active and passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100