We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I already spotted the call extern/Scheduler.runNextScheduled_() pattern:
static mkdir(path) { ensurePath_(path) mkdir_(path, Fiber.current) return Scheduler.runNextScheduled_() return await { mkdir_(path, Fiber.current) } }
And was replacing it with:
static mkdir(path) { ensurePath_(path) return await_ { mkdir_(path, Fiber.current) } }
But much like #65 it why don't we just move this responsibility into Scheduler:
Scheduler
static mkdir(path) { ensurePath_(path) return Scheduler.await_ { mkdir_(path, Fiber.current) } }
await is no doubt familiar to those doing async in JavaScript, but open to a better name...
await
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
I already spotted the call extern/Scheduler.runNextScheduled_() pattern:
And was replacing it with:
But much like #65 it why don't we just move this responsibility into
Scheduler
:await
is no doubt familiar to those doing async in JavaScript, but open to a better name...The text was updated successfully, but these errors were encountered: