Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[scheduler] Rename priority levels #13842

Merged
merged 1 commit into from
Oct 12, 2018
Merged

[scheduler] Rename priority levels #13842

merged 1 commit into from
Oct 12, 2018

Commits on Oct 12, 2018

  1. [scheduler] Rename priority levels 

    - "Interactive" -> "user-blocking"
- "Whenever" -> "Idle"

These are the terms used by @spanicker in their main-thread scheduling
proposal: https://github.com/spanicker/main-thread-scheduling#api-sketch

That proposal also uses "microtask" instead of "immediate" and "default"
instead of "normal." Not sure about "microtask" because I don't think
most people know what that is. And our implementation isn't a proper
microtask, though you could use it to implement microtasks if you made
sure to wrap every entry point. I don't really have a preference between
"default" and "normal."

These aren't necessarily the final names. Still prefixed by `unstable_`.
    @acdlite
    acdlite committed Oct 12, 2018
    Configuration menu
    Copy the full SHA
    6073e96 View commit details
    Browse the repository at this point in the history