Understanding Normal Errors vs. Defects in Effect Typescript Library
I'm trying to get my head around normal errors vs defects.
It feels odd to me that we should completely stop tracking defects at a type level.
I understand that we want 2 different channels so that we can make decisions deep in our logic over whether an error can be usefully handled, and avoid propagating that throughout our code.
The thing is.. I would still like to be able to see at a type level what defects an effect might produce, as it provides transparency and understanding about the logic an effect encapsulates.
I also might want to display those defects in different ways at the boundary of my effect, and having types is nice for that..
Does this make sense?
It feels odd to me that we should completely stop tracking defects at a type level.
I understand that we want 2 different channels so that we can make decisions deep in our logic over whether an error can be usefully handled, and avoid propagating that throughout our code.
The thing is.. I would still like to be able to see at a type level what defects an effect might produce, as it provides transparency and understanding about the logic an effect encapsulates.
I also might want to display those defects in different ways at the boundary of my effect, and having types is nice for that..
Does this make sense?
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
