Understanding Effect's Error Model: RuntimeException and UnknownException
I've been trying to understand Effect's error model in depth, but I'm confused about some of its primitives.
My current understanding is that Effect has two main categories of errors:
1. Expected Errors (Typed Errors/Failures): Appear in the error channel. Are recoverable.
2. Unexpected Errors (Defects): NOT in the error channel. NOT recoverable.
Where I get confused:
---
Questions:
- Is
- Its JSDoc says that it "is used for errors that occur at runtime but are still considered recoverable or typed." Does this mean that
- Is there a use case where I would want to create a
---
As a typed error (in
As a defect (outside
Questions:
- Why is
- Why does it exist in addition to
- Is there a use case where I would want to create a
---
I noticed
Questions:
- Is this a recommended pattern for application-level or library-level error modeling?
- How does this relate to Effect's built-in
My current understanding is that Effect has two main categories of errors:
1. Expected Errors (Typed Errors/Failures): Appear in the error channel. Are recoverable.
2. Unexpected Errors (Defects): NOT in the error channel. NOT recoverable.
Where I get confused:
---
RuntimeExceptionEffect.dieMessage()Questions:
- Is
RuntimeException- Its JSDoc says that it "is used for errors that occur at runtime but are still considered recoverable or typed." Does this mean that
RuntimeException- Is there a use case where I would want to create a
RuntimeException---
UnknownExceptionUnknownErrorAs a typed error (in
EAs a defect (outside
EQuestions:
- Why is
UnknownException- Why does it exist in addition to
RuntimeException- Is there a use case where I would want to create a
UnknownException---
I noticed
@effect/aiUnknownErrorAiErrorQuestions:
- Is this a recommended pattern for application-level or library-level error modeling?
- How does this relate to Effect's built-in
UnknownExceptionUnknownErrorUnknownException
Similar Threads
Was this page helpful?
