-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Slab::unique_iter panics when the slab is empty #73
Labels
bug
Something isn't working
Comments
Thanks for the report, we should definitely fix this. It may be necessary to special-case the slab being empty in the |
loyd
added a commit
to loyd/sharded-slab
that referenced
this issue
Oct 3, 2023
Avoid panics in `Slab::unique_iter()` in case of an empty slab. Closes hawkw#73
loyd
added a commit
to loyd/sharded-slab
that referenced
this issue
Oct 3, 2023
Fixes panics in `Slab::unique_iter()` in case of an empty slab. Fixes hawkw#73
hawkw
pushed a commit
that referenced
this issue
Oct 4, 2023
Fixes panics in `Slab::unique_iter()` in case of an empty slab. Fixes #73
hawkw
pushed a commit
that referenced
this issue
Oct 4, 2023
Fixes panics in `Slab::unique_iter()` in case of an empty slab. Fixes #73
hawkw
added a commit
that referenced
this issue
Oct 4, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Due to the
expect
inSlab::unique_iter
, the function panics when used on an empty slab.Trying to use this as a way to speed up a fork of
async_executor
, which currently usesMutex<slab::Slab<Waker>>
, but a correctDrop
impl requires at the minimum a iterator over the entire slab, and preferably a draining iterator.The text was updated successfully, but these errors were encountered: