typetools / typetools/checker-framework
More precise exception parameter and throws checking
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 440
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 134
Description
Currently, the qualifier on an exception parameter must be top. (See discussion: https://groups.google.com/d/msg/checker-framework-dev/ZeqztsBXW4M/aBC2A4J5y2UJ)
For checked exceptions, a more precise qualifier could be allowed, if more precise type checking was implemented for exception parameters, thrown expressions, and throws clauses.
Original issue reported on code.google.com by Suzanne....@gmail.com on 7 Jan 2015 at 6:20
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 linked Checker Framework discussion to understand the intended qualifier rules. Then trace how exception parameters, thrown expressions, and throws clauses are checked. Done means implementing and validating more precise checking for checked exceptions, including appropriate coverage for all three cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100