Scala 3 migration
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 376
- Forks
- 66
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
Dotty-compatibility mode provides a way to use mouse now in Scala 3 projects, eg
("org.typelevel" %% "mouse" % "0.25").withDottyCompat(dottyVersion)
However, Scala 3 migration is also a good time for any major refactors of the lib. Im thinking about a Scala 3 only version which would allow a clean break.
- Top level values and extension methods
- Dropping any obsolete methods that are now in core
- Move to munit for testing (just for the simplicity)
If you have any ideas/requests for a Scala 3 rewrite, please add them to this issue
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 Scala 3 migration checklist and the existing Dotty-compatibility setup described in this issue. Confirm which migration items are already complete, then identify and agree on the remaining refactors or requests before making changes. Done means a defined Scala 3-only migration scope with the agreed refactors completed and tests migrated to munit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100