-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Async-context formalization and diagnostics support #107
Comments
I assume the above is meant as "without additional signals" / "in the scope of the formal language described in the paper"? E.g. the following doesn't use "real" Promises but still de-facto has different linking/causal context if I understand it correctly: var connection;
var queued = [];
function runWithConnection(cb) { // userland E-Then
if (connection) { cb(connection); }
else { queued.push(cb); }
}
function setConnection(c) { // userland E-Resolve
connection = c;
queued.forEach(f => f(c));
}
setConnection(net.connect(/* ... */)); // ~ calling E-Resolve
runWithConnection(postConnect); // ~ calling E-Then Nevermind, looks like the paper includes that in the context tracking instead of trying to include it in the more general abstractions. |
Would it make sense to collect these in a runnable form? E.g. starting an acceptance suite that just defines the cases but not even necessarily the expected values for causal and/or linking context? |
FYI the (very rough) draft of this formalization is here: https://github.com/mike-kaufman/async-context-definition. It's still rough, look for more of it to fill out over the next month. |
should this remain open? [ I am trying to chase dormant issues to closure ] |
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made. |
Updating text here to better reflect reality - mike-kaufman
Current Status:
f = () = > { setTimeout(f, 1000); }
)The text was updated successfully, but these errors were encountered: