Join GitHub today
consolidate redundant frame/call stack tracking #210
Both these seem to accomplish the same thing:
The later is maybe more general so can try consolidating to that.
Another enhancement may be to wrap accesses/modifications to that frame stack in a new thread-safe API/structure. Reason being that it's otherwise difficult for plugins to passively observe/sample the script-layer call stack (can't use a BIF because that changes call stack, can't use hooks in main thread because it's also important to know how much time is not spent in script-layer, so naturally would turn to requiring thread-safe access from external plugin thread).