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.
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
[WASI] timers based on wasi:clocks #105879
[WASI] timers based on wasi:clocks #105879
Changes from all commits
d19d317
4217313
1872580
d3586a5
b9f4243
3129ac4
31006e4
3ca5606
b14f61a
0ad3fe5
00eab2f
186d55d
7b2d74e
e95a702
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is probably too naive solution.
There could be other pending tasks scheduled to C# thread pool.
But not in the await chain leading to this entrypoint.
Such code/tasks/continuations could have (expected) externally observable side effects (after we exit the entry point).
But I don't know how to do that at this point. So I guess it will be some next PR.
cc @dicej
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the browser we schedule browser callback any time the new job triggers
ThreadPool.RequestWorkerThread()
, but we could not do it here.Maybe we need to run
ThreadPoolWorkQueue.Dispatch();
until there was no call toThreadPool.RequestWorkerThread()
before we return from the entry point.cc @SingleAccretion , any thoughts ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that full event loop emulation requires what is effectively:
I think it's ok to wait for the top-level task only here. It matches "normal" platform's behavior:
So it seems unlikely our tests would depend on it.
It does not match Browser's behavior, of course. It is a point to debate whether we'd want the eventual async main experience to match browser or not-browser.