Stack traces about promises-spec HOT 5 CLOSED

Stack trace manipulation isn't very well specified (hopefully this will change), and it's fraught with performance issues (which is unlikely to change any time soon). As such it shouldn't be part of the spec. Incidentally if you're using the latest version of Q you can control how much stack trace info will be kept by using Q.longStackJumpLimit. You should set it to 0 in production, and be aware that very large numbers will cause serious memory issues for long promise chains. I think it defaults to about 2

from promises-spec.

@ForbesLindesay for the record on Q: 0.8.5 onward has had one-level "long" stack tracing, with the ability to control it only introduced in the unreleased Q 0.9. It's defaulting to 1 right now, since I still haven't written the code to stitch together multiple jumps, but hopefully before 0.9 is released multiple levels will be allowed with a default of maybe 5.

But yes, I agree that this isn't something we can really specify or mandate, for performance reasons if nothing else.

Although, maybe coming up with a standard for long traces generally would be good? Maybe not within scope of Promises/A+, but standardizing on "From previous event:" or similar would be nice!

from promises-spec.

Would be interesting to see if two libraries that both did long stack traces (with several jumps) could be made to inter-operate nicely to produce the full long stack trace from both libraries.

from promises-spec.

^ oh woah, interesting idea.

from promises-spec.

I don't know of any other libraries that do it though.

from promises-spec.