[PATCH] Split Data.IntMap into Data.IntMap.Strict and Data.IntMap.Lazy.

Malcolm Wallace malcolm.wallace at me.com
Mon Oct 3 09:49:45 CEST 2011

>> +1 for both .Strict and .Lazy.
> +1 as well from me

+1 from me.

> (Just wondering: would there be a transitional compatibility layer, or
> would all user-code have to change the Data.Map imports at once with the
> new containers version implementing this proposal?)

I assume that Data.Map will essentially re-export everything from Data.Map.Lazy, and if you have used a prime'-ed-for-strictness variant, then you will need to add an import of Data.Map.Strict, qualify the function, and remove the prime.


More information about the Libraries mailing list