viperproject / viperproject/silver
Scala 3, compiler warnings, IntelliJ suggestions
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 100
- Forks
- 53
- Avg merge
- 8h 10m
- Merged PRs (30d)
- 2
Description
When updating to Scala 3, we should also attend to the 60+ compiler warnings, and the numerous IntelliJ code improvement suggestions.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. Start by locating the Scala 3 compiler warnings and IntelliJ suggestions across the repository, then determine which are actionable. Done means the relevant warnings have been addressed and the suggestions have been evaluated or resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100