JSpecify

Open
#87 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
tooling

Research direction

Start with the referenced lang/frontend/language/src/main/java/tools/vitruv/neojoin/package-info.java and inspect how JSpecify annotations are applied across the frontend, model, backend-emf, and backend-tgg modules. Determine whether module-level annotation is supported, then ensure the remaining backend-tgg module uses nullability annotations and that existing coverage remains intact.

Written by the indexing model from the issue text.

Description

refactoring

Parts of the codebase already use JSpecify nullability annotations. This includes the frontend, model and backend-emf. Currently, this is enforced by annotating each package with @NullMarked:

https://github.com/vitruv-tools/NeoJoin/blob/9549ababecf80f47114c0c175c73191a1ac45ece/lang/frontend/language/src/main/java/tools/vitruv/neojoin/package-info.java#L1-L4

It should be investigated whether this can be simplified by annotating the module instead, which would only require a single annotation per module instead of one for each package. Also, the remaining modules (backend-tgg) should be converted to use nullability annotations.

Dominant language
Java
Stars
3
Forks
5
Avg merge
12h 49m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vitruv-tools/NeoJoin

All issues in vitruv-tools/NeoJoin

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.