Timeline for How could a computer program do anything if everything is immutable?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 30, 2020 at 18:52 | comment | added | Euphoric | @JörgWMittag Thanks for clarification. I don't think that level of detail is necessary for my answer. | |
| Sep 30, 2020 at 18:44 | comment | added | Jörg W Mittag |
For example, the State monad can still guarantee that you won't format the hard disk or launch the missiles, but the IO monad can't.
|
|
| Sep 30, 2020 at 18:43 | comment | added | Jörg W Mittag |
For state, you wouldn't use the IO monad, but a more restricted one. IO means "any side-effect at all" which also means "absolutely no guarantees". For state, the State monad would be more appropriate, or even more restricted, the Reader or Writer monad. One interesting thing about the State monad is that you can have a SoftwareTransactionalMemory monad or a DistributedDatabase with the same interface, so you can parallelize and / or distribute your code without changing how it interacts with state
|
|
| Sep 30, 2020 at 18:29 | history | answered | Euphoric | CC BY-SA 4.0 |