Understanding `Effect.die` in Non-Concurrent Applications
I am trying to understand using
doesn't encountering an error already stop execution and the function returns? So you would recurse up the stack till the error is handled? If that is the case then why would you want to use
https://effect.website/docs/error-management/unexpected-errors/
Effect.die . The docs say that die kills the currently running fiber, however if you don't have any concurrency in your application then don't you have only one fiber? Hence you will kill your program if you die?doesn't encountering an error already stop execution and the function returns? So you would recurse up the stack till the error is handled? If that is the case then why would you want to use
Effect.die in any sort of production non concurrent application?https://effect.website/docs/error-management/unexpected-errors/
Effect Documentation
Understand how Effect handles unexpected errors with tools to manage defects, terminate execution, and selectively recover from critical failures.
