diff options
| author | Andreas Hindborg <a.hindborg@kernel.org> | 2026-06-05 12:56:31 +0200 |
|---|---|---|
| committer | Danilo Krummrich <dakr@kernel.org> | 2026-09-29 21:04:59 +0200 |
| commit | d190aa209416f6d6d7bdaffffaaab2af5d3ccdec (patch) | |
| tree | cfaabd4fcc8e4ee570a14300070c7d8bfe25ef00 /tools/lib/python/kdoc/python_version.py | |
| parent | 82134823a07b4f45096a287f790c169511859617 (diff) | |
| download | linux-next-d190aa209416f6d6d7bdaffffaaab2af5d3ccdec.tar.gz linux-next-d190aa209416f6d6d7bdaffffaaab2af5d3ccdec.zip | |
rust: alloc: allow different error types in `KBox::pin_slice`
Previously, `KBox::pin_slice` required the initializer error type to match
the return error type via `E: From<AllocError>`. This prevented using
infallible initializers like `new_mutex!` inside `pin_slice`, because
`Infallible` does not implement `From<AllocError>`.
Introduce a separate type parameter `E2` for the initializer error type
and require `E: From<AllocError>` and `E: From<E2>` instead. This allows
the initializer to return a different error type that can be converted
into the final error type, enabling use of infallible pin initializers
in fallible allocation contexts.
Link: https://rust-for-linux.zulipchat.com/#narrow/channel/288089-General/topic/.E2.9C.94.20Constructing.20Mutex.20from.20PinInit.3CT.2C.20Error.3E
Co-developed-by: Benno Lossin <lossin@kernel.org>
Signed-off-by: Benno Lossin <lossin@kernel.org>
Signed-off-by: Andreas Hindborg <a.hindborg@kernel.org>
Link: https://patch.msgid.link/20260605-pin-slice-init-v2-1-b197e84040ba@kernel.org
Signed-off-by: Danilo Krummrich <dakr@kernel.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions