I was surprised when I learned that Data.Map.Strict.Map is not strict. Its laziness has serious consequences for attempts at space leak free programming in Haskell. Here’s an article I wrote about it:
The usual FUD about space leaks and laziness…
What would you say is the counterpoint?
I’ve seen laziness and “space leaks” cost companies a lot of money, hiring expensive consultants (who couldn’t fix it), spending lots of money on amazon 64GB instances, having 2+ hours of deployment times… until someone figured out the issues, which required a lot of GHC knowledge and debugging.
So to me, those are pretty real concerns.
This might work for you。ghc-9.2.1 support that.