The current call stack implementation looks more or less like a full trace from evaluation. Moving around in that trace updates the local variable bindings just as expected, so the feature is already quite useful! But only if you understand it in the first place. The format of the trace makes that less likely to happen for anyone not intimately familiar with OPA eval internals, and it'd be great if we would figure out a way to make it look more like what users are familiar with from other languages. I'm thinking that'd involve filtering the trace only on rule enter events, and perhaps format them a little nicer. But anything that makes the stack a little less intimidating is progress in the right direction.
Regal DAP
Comparison to GoPls DAP
The current call stack implementation looks more or less like a full trace from evaluation. Moving around in that trace updates the local variable bindings just as expected, so the feature is already quite useful! But only if you understand it in the first place. The format of the trace makes that less likely to happen for anyone not intimately familiar with OPA eval internals, and it'd be great if we would figure out a way to make it look more like what users are familiar with from other languages. I'm thinking that'd involve filtering the trace only on rule enter events, and perhaps format them a little nicer. But anything that makes the stack a little less intimidating is progress in the right direction.
Regal DAP
Comparison to GoPls DAP
