Proposal: Value strict versions of containers

Edward Z. Yang ezyang at MIT.EDU
Mon May 23 12:08:42 CEST 2011

I'm warming up to the same underlying type approach.  Unfortunately, it's
not fully general (for example, you couldn't use this to manage lazy/strict
bytestrings) but I could see this spreading to other libraries (e.g. transformers)


Excerpts from Edward Z. Yang's message of Sun May 22 07:04:20 -0400 2011:
> Unsure, ask again in a few days.
> Benefits for encoding at the data type level:
>     1. You'll never "forget" to add an appropriate `seq`, so the
>        code looks essentially the same in the lazy and strict cases.
>     2. It's true that converting between lazy and strict maps can
>        be something of a pain. However, I suspect that it is good discipline
>        to know what strictness your map is (I may be wrong here.)
> Cheers,
> Edward

More information about the Libraries mailing list