-
Notifications
You must be signed in to change notification settings - Fork 527
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backport Scala Native support to 3.3.x #3138
Backport Scala Native support to 3.3.x #3138
Conversation
3316e80
to
d913dff
Compare
d913dff
to
5d11fe9
Compare
I've published
|
CI is green in all linked PRs. At this point I think it's fair to say we have a viable ecosystem on Cats Effect Native :) If there are no objections (@djspiewak, @vasilmkd?) in the next couple days I would like to backpublish native artifacts based on this branch as v3.3.14. This will unblock the ecosystem. The 3.3.x series has been extremely stable for nearly a year now (no forwards/backwards binary changes). So I don't anticipate any problems maintaining this branch in parallel. When Cats Effect finally updates to Scala 3.1+ we can merge this branch in (or preferably #3057, where the actual work was done). |
Now behaves like `ScheduledExecutorService#setRemoveOnCancelPolicy(true)` used on JVM
I've published |
This reverts commit 7efbac0.
In addition to CI, the entire test suite passes on my local macOS Intel. |
Backport of #3057.
Unfortunately this can't be merged directly into
series/3.3.x
because it bumps Scala 3 to 3.1. But it can exist in parallel.