@viktorklang @runarorama they don't have destructive reassignment, not to be confused with reassignment.
-
-
Replying to @dibblego
@dibblego That's a very valid point. /cc@runarorama1 reply 0 retweets 0 likes -
Replying to @viktorklang
@viktorklang@runarorama see scalaz.effect.{ST, IO} for modelling reassignment such that it is not destructive (pure functional var).1 reply 1 retweet 1 like -
Replying to @dibblego
@dibblego@viktorklang@runarorama I don't speak Scala, but in Haskell ST and IO are definitely destructive and not purely-functional2 replies 0 retweets 0 likes -
Replying to @acfoltzer
@acfoltzer@viktorklang@runarorama Can you show me what distinguishes IO/ST and say [] in that only the former is destructive?1 reply 0 retweets 0 likes -
Replying to @dibblego
@dibblego@viktorklang@runarorama maybe you have ST/IO refs confused with State monad? surely mutable heap cells are obviously destructive4 replies 0 retweets 0 likes -
Replying to @acfoltzer
@acfoltzer@viktorklang@runarorama ST/IO do not have destructive reassignment any more than anything else (i.e. not at all).2 replies 0 retweets 0 likes -
Replying to @dibblego
@dibblego@viktorklang@runarorama could you give me a link explaining this? I must have the wrong definitions in mind2 replies 0 retweets 0 likes -
Replying to @acfoltzer
@acfoltzer@viktorklang@runarorama there is nothing about IO/ST that breaks equational reasoning (observing destructive update).1 reply 0 retweets 0 likes -
Replying to @dibblego
@dibblego@viktorklang@runarorama you certainly can observe it with threads (thus why I agree on ST -- no threads there)1 reply 0 retweets 0 likes
@acfoltzer @viktorklang @runarorama twitter is shit for meaty discussion. IRC?
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.