Do you know what the following mean in a heap profile? _apply3 is the one I'm particularly interested in.

Prelude._apply3 Prelude._apply1

They have the following definitions: _apply3 f a b c = f a b c _apply1 f a = f a They are introduced internally by the compiler, basically to ensure the correct lazy semantics at certain points. Ideally, the heap profiling code ought to hide them from the user, and re-attribute their costs to the 'f' that they are disguising. Regards, Malcolm