Notices by Stephen Kell (stephenrkell@recurse.social)

@wingo @ltratt @cfbolz Time for my pedantry... let's not mix 'stack traces' (a debugging feature) with 'stack frame' (a memory allocation). Stack traces already include 'frames' that do not correspond to any physical frame, thanks to inlining

(That is another example of something that can be done at -O0, via always_inline, and straddles 'correctness' vs 'optimisation'. For TC[O] it depends whether you classify asymptotic space usage as functional or extrafunctional... the use case matters.)

@cfbolz @wingo Tangential, but one of the tricky things I sometimes think about is how to reconcile tail-call optimisation with debuggability. Do you have a take?

E.g. with tail recursion, even supposing you can reconstruct the stack depth and locals from ambient other state, it's not expressible within DWARF to 'synthesise n frames, computed like so'... and it'd probably be a misfeature even if it were. What should happen?

Sibling tail-call opt is even trickier... I often tell it to -f off.