The current trace API does not really provide helpful information:
The events are from the point of view of the backend, and not really from the point of view of fibers.
Some events are missing information such as caller and the originating fiber (for example, when a fiber is scheduled, we want to know from where it was scheduled, and in the context of which fiber).
We also need to be able to transform the information for each event, provided as an array of values (for performance and simplicity), into something more meaningful - a hash, that we could later transform into nicely formatted text.
The current trace API does not really provide helpful information:
callerand the originating fiber (for example, when a fiber is scheduled, we want to know from where it was scheduled, and in the context of which fiber).We also need to be able to transform the information for each event, provided as an array of values (for performance and simplicity), into something more meaningful - a hash, that we could later transform into nicely formatted text.