Overhead and Clarity of Wrapping Pure Functions in ZIO/Effect
Just watched this talk: https://youtu.be/nZAxtQAJaU0?si=naM3-IcpwzkVNyc_
tdlr is: wrapping pure functions in a ZIO/Effect has non-negligible overhead and you should use option, either, etc
as well as wrapping it in a ZIO/Effect makes it less clear that that code is in fact pure
I know this came up in threads like this in the past: dataThe Disappearance of `Either.liftThrowable`
where my understanding was the answer was just: "use an Effect anyway or use an Exit"
is that still the currently held perspective?
tdlr is: wrapping pure functions in a ZIO/Effect has non-negligible overhead and you should use option, either, etc
as well as wrapping it in a ZIO/Effect makes it less clear that that code is in fact pure
I know this came up in threads like this in the past: dataThe Disappearance of `Either.liftThrowable`
where my understanding was the answer was just: "use an Effect anyway or use an Exit"
is that still the currently held perspective?
YouTubeZiverge
"The Cost Of Your ZIO Addiction" by Jules Ivanic at ZIO World 2023.
In this presentation, Jules takes us on a deep dive into the world of functional Scala development and the benefits of using effect systems like ZIO. However, he also cautions about the risks of over-reliance, reminding us that "The dose makes the poison." Explore common ZIO m...
In this presentation, Jules takes us on a deep dive into the world of functional Scala development and the benefits of using effect systems like ZIO. However, he also cautions about the risks of over-reliance, reminding us that "The dose makes the poison." Explore common ZIO m...
Similar Threads
Was this page helpful?
