| Crates.io | once-list2 |
| lib.rs | once-list2 |
| version | 0.4.0 |
| created_at | 2024-12-04 08:12:07.483038+00 |
| updated_at | 2026-01-22 09:30:29.65102+00 |
| description | A single linked list which is backed by `OnceCell`. You can append the value to the non-mutable `OnceList`. |
| homepage | |
| repository | https://github.com/wada314/once-list |
| max_upload_size | |
| id | 1471675 |
| size | 86,836 |
This library is a natural extension of the std::cell::OnceCell (or its original crate once_cell) library. This library provides a single-linked list OnceList type that allows you to store multiple values in a single OnceList instance even without the need for the mutability.
If you need faster operations, consider enabling caching modes:
OnceListWithLen<T, A>: O(1) len()OnceListWithTail<T, A>: fast repeated tail inserts (e.g. push_back() / extend()); does not make back() O(1)OnceListWithTailLen<T, A>: both (len O(1) + fast tail inserts)once_cell - The original crate that provides a OnceCell type. If you only need to store a single value, this crate is quite enough.elsa - A crate that provides Frozen collection types that allows you to store multiple values without the need for the mutability. They provides something similar to Vec or HashMap, so if your use case requires more than 3-ish values or you need more complex data structure than a single-linked list, then you should use this crate instead.By default, none of the features are enabled.
nightly: Enables the nightly-only features.
allocator_api std unstable feature. Note that even without this feature, this crate still supports the allocators thanks to the allocator_api2 crate.OnceList for more details.sync: This library internally uses std::cell::OnceCell which is not thread-safe. When you enable this feature, this library uses the thread-safe std::sync::OnceLock instead.
OnceListWithLen / OnceListWithTail / OnceListWithTailLen) are intentionally "single-thread oriented" and use Cell internally, so they do not implement Sync and cannot be shared across threads.
If you need multi-thread access, use the default OnceList (no-cache mode), and ensure T / allocator types satisfy the usual Send/Sync bounds.