-
Notifications
You must be signed in to change notification settings - Fork 536
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
Create UnsafeNonFatal for use in the fiber runtime #4263
base: series/3.6.x
Are you sure you want to change the base?
Conversation
Thanks for the PR!! Sorry, would you mind re-targeting to the |
569d1c9
to
ee6f0b8
Compare
Done. |
3970f74
to
58a9c5d
Compare
core/shared/src/main/scala/cats/effect/unsafe/UnsafeNonFatal.scala
Outdated
Show resolved
Hide resolved
core/shared/src/main/scala/cats/effect/unsafe/UnsafeNonFatal.scala
Outdated
Show resolved
Hide resolved
0a76d0f
to
dd85c6f
Compare
* Change visibility to only be used in `cats-effect` * Change implementation to not allocate `Some` if Fatal.
7d6dc58
to
83fecb9
Compare
Note, there is a reference to |
Creates a custom
NonFatal
type for use in the fiber runtime. This is needed because while application code generally shouldn't catchInterruptedException
, the fiber runtime is responsible for dealing with interrupts gracefully.Initially I considered naming this
RuntimeNonFatal
, however I thinkUnsafeNonFatal
makes it really clear that you shouldn't use it without knowing what you are doing.Will resolve #4254