| 22:55 | <snek> | idea that popped into my head a few minutes ago while looking at some debugging tooling that someone made... what if you could attach metadata to stack traces to identify specific function invocations?
for example lets say you have something like an event emitter, you could do something like
class Emitter {
emit(name, data) {
System.setStackMetadata(name);
// ...
}
}
and then in a stack trace, it would be identified as emit (event name) instead of just emit
|
| 22:58 | Chris de Almeida | cries in stalled error stacks proposal |
| 23:04 | <Ashley Claymore> | idea that popped into my head a few minutes ago while looking at some debugging tooling that someone made... what if you could attach metadata to stack traces to identify specific function invocations?
for example lets say you have something like an event emitter, you could do something like
class Emitter {
emit(name, data) {
System.setStackMetadata(name);
// ...
}
}
and then in a stack trace, it would be identified as emit (event name) instead of just emit
I've wanted that for some stuff too! |
| 23:04 | <snek> | error stacks proposal would be nice |
| 23:04 | <snek> | ljharb: what was the holdup on that |
| 23:07 | <Chris de Almeida> | ljharb: what was the holdup on that I think web platform folks asked for the ocean to be boiled |