typelevel / typelevel/cats-effect
Run the `IOAppSpec` on Native
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 2.2k
- Forks
- 576
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 18
Description
Another one I punted from my original PR.
In principle this is quite straightforward: we can re-use the existing technique of actually running the spec on the JVM but pointing it at either a JVM / JS / Native executable.
Because you cannot select a main method at runtime like JVM, it will also need to copy the JS technique of having a special main that emulates this behavior to choose from the various IOApps.
Finally, the tests will need to be subset again for the stuff we have not implemented on Native (like anything needing signal handlers).
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 comparing the existing JVM and JS techniques for running IOAppSpec and inspect how the JS entry point selects among IOApps. Identify which tests require unsupported Native features such as signal handlers and determine how the Native spec should be subset. Done means IOAppSpec runs on Native with the unsupported tests excluded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- build-system, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100