You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now, STRef and Ref can be unified, allowing for code reuse. Similar for STArray and something I don't think exists yet (useful for fixing purescript-node/purescript-node-process#8).
When you have a library that already uses ST, but you want to use it from Effect (for example STArray; I've been using MVector lately in Haskell in both IO and ST, for production and testing respectively).
Granted, explicit liftST is enough for that, you don't need the constraint for all the operations (it would just be more convenient).
Activity
garyb commentedon Apr 30, 2018
Moving everything to use
MonadSTconstraints would destroy the ability to optimizeSTI think (not that it is optimized in the 0.12 RC just now).Honest question: why/when would you want to do this? I can't think of any situations where I've wanted a non-closed ST.
no-longer-on-githu-b commentedon Apr 30, 2018
When you have a library that already uses ST, but you want to use it from Effect (for example STArray; I've been using MVector lately in Haskell in both IO and ST, for production and testing respectively).
Granted, explicit liftST is enough for that, you don't need the constraint for all the operations (it would just be more convenient).
eric-corumdigital commentedon Jan 4, 2019
Am wanting to use STObject in Effect. Got my upvote.