It would be interesting to visualise the call stack over time as effects are performed, handled, and resumed. LLVM's x-ray supports annotating functions to be included in traces. This would already give all the information, but the compiler could map the function names back to source-code ranges (corresponding to parts of functions.
It could be fun to show a call-stack-over-time graph in the language playground based on this.
LLVM has some tools for converting traces to be viewable in perfetto/flamegraph.
It would be interesting to visualise the call stack over time as effects are performed, handled, and resumed. LLVM's x-ray supports annotating functions to be included in traces. This would already give all the information, but the compiler could map the function names back to source-code ranges (corresponding to parts of functions.
It could be fun to show a call-stack-over-time graph in the language playground based on this.
LLVM has some tools for converting traces to be viewable in perfetto/flamegraph.