Should Effect type be used only for computations with possible side effects?
In the Effect docs I found the line:
(https://effect.website/docs/getting-started/creating-effects/)
It's easy to note, that the function in the example is side effect free, but still it's the example in the docs.
So either the example is bad or the line about side effects in a computation represented with Effect is wrong. What is the case?
(https://effect.website/docs/getting-started/creating-effects/)
Effect provides different ways to create effects, which are units of computation that encapsulate side effectsSo Effect should represent a computation with side effects. But later on the same page of the docs an example of using Effect is present:
It's easy to note, that the function in the example is side effect free, but still it's the example in the docs.
So either the example is bad or the line about side effects in a computation represented with Effect is wrong. What is the case?
Effect Documentation
Learn to create and manage effects for structured handling of success, failure, and side effects in synchronous and asynchronous workflows.
Similar Threads
Was this page helpful?
