Stop using "Int" for microsecond delays in "base"

Johan Tibell johan.tibell at
Wed Mar 30 20:00:27 CEST 2011

On Wed, Mar 30, 2011 at 7:56 PM, Evan Laforge <qdunkan at> wrote:
> It's good for big data structures since it can be unpacked into the
> constructor.  I've seen space usage go down by 1/3 after an Integer ->
> Int switch.  Integer is a sum type so there's an extra two words of
> overhead (if not mistaken, one for the tag, and one for the
> indirection since it can't unpack).

Yes. Integer is terrible for performance.

More information about the Libraries mailing list