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

Use crossbeam_deque::Injector instead of crossbeam_queue::SegQueue #791

Merged
merged 1 commit into from Aug 24, 2020
Merged

Use crossbeam_deque::Injector instead of crossbeam_queue::SegQueue #791

merged 1 commit into from Aug 24, 2020

Commits on Aug 17, 2020

  1. Use crossbeam_deque::Injector instead of crossbeam_queue::SegQueue 

    `Injector` and `SegQueue` are _almost_ identical, down to the very same
comments in their implementations. One difference is that `Injector`
allocates its first block as soon as it's created, but `SegQueue` waits
until its first `push`, which complicates it to allow being `null`.
`Injector` also has methods to steal batches into a deque `Worker`,
which might be useful to us.

At the very least, this lets us trim a dependency.
    @cuviper
    cuviper committed Aug 17, 2020
    Configuration menu
    Copy the full SHA
    c7d963a View commit details
    Browse the repository at this point in the history