typetools / typetools/checker-framework
Is there a way to add aliases for third-party annotations?
A pull request for this has already been merged.
- #3626 by @mernst — merged
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 440
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 134
Description
I came across custom annotations: https://github.com/janino-compiler/janino/tree/9ef0cfa9057167739211912da564054a7f3083d7/commons-compiler/src/main/java/org/codehaus/commons/nullanalysis
Just in case, janino-compiler targets Java 1.6, so it looks like they can't use type annotations yet.
Is there a way to make checker-framework understand janino-compiler nullability annotations?
I guess janino-compiler project wants to have zero-dependencies (which makes sense as the compiler is often embedded in weird class generation use-cases).
Is there something like astub for annotations in checker-framework?
Is there a way to write zero-dependency code yet make it compatible with checker-framework analysis?
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 reviewing the custom annotation definitions linked in the issue and the merged pull request #3626. Determine whether that work addressed aliases or stub-like support for janino-compiler annotations; the issue is complete only when a supported compatibility path is confirmed and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100