Oversaturated Arguments for Tail Calls

[iamrecursion]

Summary

Currently we have handling for oversaturated arguments in all cases except that of the tail-call-optimised function. As the tail-call optimisation logic is going to change dramatically in the face of the CPS transform, it seems like wasted effort to implement a significant extra amount of code only to have it change later.

This issue exists to track the implementation of this functionality once the CPS transformation has been implemented.

Value

Comprehensive handling of oversaturated function applications.

Specification

• Develop a design for how to handle oversaturated function applications in the face of CPS and the associated tail-call optimisation.
• Implement this design, ensuring that it doesn't result in any undue performance regressions.

Acceptance Criteria & Test Cases

• TCO'd functions hand have oversaturated applications without causing a stack overflow.

[kustosz]

Just a note though, as the description is overly pessimistic. We're still not sure if it's possible to construct a case that would break the current logic.