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
Well the point is that (at least at a hight level), there's no reason that mutable containers should be tied to STM. If I want to use a mutable hashmap from ST so that I can have the most efficient possible algorithm in my pure function, there's no reason it can't be the same hashmap implementation as the one I'd use in STM.
From the abstraction perspective this seems like a good idea. However, generalising it in such a way would complicate the API and what's worse, would make it harder to optimise the algorithm.
@ElvishJerricco pointed out this possibility. What do you think?
The text was updated successfully, but these errors were encountered: