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.

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

Unify run loop setup. #16217

Merged
merged 2 commits into from
Feb 6, 2018
Merged

Conversation

rwjblue
Copy link
Member

@rwjblue rwjblue commented Feb 5, 2018

Declare run-loop queues in single centralized location.

Prior to this change the list of queue names was mutated after the backburner instance was instantiated. This sort of private API manipulation is problematic because Backburner may move to an alternative internal structure.

This also makes it much much easier to grok the actual queues in the system and their ordering...

Prior to this change the list of queue names was mutated _after_ the
backburner instance was instantiated. This sort of private API
manipulation is problematic because Backburner may move to an
alternative internal structure.

This also makes it much much easier to grok the actual queues in the
system and their ordering...
This queue is _never_ intended to be scheduled into by anyone other than
Ember itself, this change makes that much more likely.
@rwjblue
Copy link
Member Author

rwjblue commented Feb 5, 2018

@krisselden - This also makes rsvpAfter a "private" queue...

@krisselden krisselden merged commit 0435add into emberjs:master Feb 6, 2018
@mmun mmun deleted the unify-run-loop-queues branch February 6, 2018 03:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants