Understanding Immutability in Effects and Its Benefits
This might sound really dumb but i would really appreciate if someone could help me with this, I needed some more clarity as to why we call Effects "immutable" and how does that differ from usual non-effect code. What gains do we receive when using this "immutability" of effect over code that isn't.
Does this immutability basically infer that effects are self contained, lazily executed, instruction sets which won't mutate any global state on their own unless ran explicitly? or... ? :/
Does this immutability basically infer that effects are self contained, lazily executed, instruction sets which won't mutate any global state on their own unless ran explicitly? or... ? :/
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
