@viktorklang They do have assignment and reassignment. That operation is called flatMap. #flatmapthatshit
-
-
Replying to @runarorama
@runarorama flatMapping that shit doesn't change the state o the previous "step". Logical progression/ordering is distinct from reassign IMO1 reply 0 retweets 0 likes -
Replying to @viktorklang
@viktorklang Well, that all depends on your definitions of "previous" and "state".1 reply 0 retweets 0 likes -
Replying to @runarorama
@runarorama It always depends on definitions, doesn't it. What would life be without discussions of semantics ;-)2 replies 0 retweets 0 likes -
Replying to @viktorklang
@viktorklang@runarorama they don't have destructive reassignment, not to be confused with reassignment.1 reply 0 retweets 0 likes -
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
@acfoltzer @viktorklang @runarorama No, there is no confusion, nor destructive update.
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.