4 ms·
The lost stack traces aren't necessarily unrecoverable, it's still possible to have useful "stack traces" in trampolined/tcoed code without direct support from
by pshirshov 4y ago
The lost stack traces aren't necessarily unrecoverable, it's still possible to have useful "stack traces" in trampolined/tcoed code without direct support from the language runtime.
First time we've (7mind) implemented that in ZIO in 2019 ( see https://m.youtube.com/watch?v=mGxcaQs3JWI https://m.youtube.com/watch?v=mGxcaQs3JWI ), now it's a norm in Scala world.
- soegaard 4y agoI am curious, did you look at "continuation marks" too?
- pshirshov 4y agohttps://docs.racket-lang.org/reference/contmarks.html https://docs.racket-lang.org/reference/contmarks.html ? Nope. But from what I see that's a dnfferent story, there you have support from the language runtime, if you have that the problem is trivial.
- soegaard 4y agoYes, a different story. The idea is that attaching information on "stack frames" might be useful for other things than stack traces. The reference linked to is precise, but do not show the utility. The rationale here gives a better quick introduction: > https://srfi.schemers.org/srfi-157/srfi-157.html https://srfi.schemers.org/srfi-157/srfi-157.html A more thorough treatment: https://www2.ccs.neu.edu/racket/pubs/dissertation-clements.pdf https://www2.ccs.neu.edu/racket/pubs/dissertation-clements.p...