Realized (yet again) that while events in an emitter may form a DAG, during execution they very much form a tree. This is the same as with regular functions. Any given function may be called by many other functions. But it never has multiple callers simultaneously — so a tree!
-
-
(I know there is a tracing command available already, but that's only a timeline right now — it's much easier to spot patterns by looking at (sorted) aggregates such as (differential) flamegraphs / flamescopes)
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.