The Pathological Case of Heap Allocation in a Functional Programming Language

In a programming language like rock which is purely functional the way that you try to express all your effects is you say okay please go perform this effect for me and then call this function after you do that effect. But it's exactly the pathological case that I just described. It's a function that's capturing many other functions that happen after you do it in a practical computation. And so the type checker has to deal with that. This is actually one reason that rock can't work immediately out of the box with something like sub typing because why we need this thing we're like an ABC has to be exactly ABC.