typetools / typetools/checker-framework
Multiple dependent type annotations end up in bytecode
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 440
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 134
Description
Dependent type annotations are standardized, @KeyFor("field") => @KeyFor("this.field). Javac inserts the explicitly written annotation into bytecode, @KeyFor("field"). The Checker Framework inserts the standardized annotation into bytecode, @KeyFor("this.field). So both annotations end up in bytecode, but only the standardized annotation should. (DependentTypesHelper works around this problem.)
See also https://github.com/typetools/checker-framework/pull/674.
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 DependentTypesHelper and the related discussion in pull request 674. Reproduce the dependent annotation case described in the issue and inspect the generated bytecode. Done means the explicitly written and standardized forms no longer both appear in bytecode; only the standardized annotation should remain.
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
- 35/100