format: add activation identifier to correlate invocations with returns#245
Merged
Conversation
Contributor
|
An invocation and the return (or revert) that ends the same activation can now carry a matching `activation` string. A debugger uses it to pair a call with its return directly — independent of trace order, without relying on strictly nested invoke/return ordering. Distinct activations carry distinct values, unique within a program. - Schema: add an optional `activation` string to the invoke, return, and revert contexts; add a worked example pairing an invoke with its return by a shared value. - TS types: add `activation` to the invoke/return/revert types and validate it in their guards.
gnidan
force-pushed
the
architect-name-activation
branch
from
7bead51 to
e9cb163
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An invocation and the return (or revert) that ends the same activation can now carry a matching
activationstring. A debugger uses it to pair a call with its return directly — independent of trace order, and without relying on invoke/return being strictly nested. Distinct activations carry distinct values, unique within a program.activationstring to the invoke, return, and revert contexts; add a worked example pairing an invoke with its return by a shared value.activationto the invoke/return/revert types and validate it in their guards.