diff options
author | 2023-05-02 12:40:15 +0000 | |
---|---|---|
committer | 2023-05-31 18:53:10 +0200 | |
commit | 4a59081c09cbfe17505baf3db50ebb9b97290bae (patch) | |
tree | e6fa3f0dc0f650ba8be998ed47ad41ddbd2de6a8 /scripts/generate_rust_analyzer.py | |
parent | rust: init: update macro expansion example in docs (diff) | |
download | wireguard-linux-4a59081c09cbfe17505baf3db50ebb9b97290bae.tar.xz wireguard-linux-4a59081c09cbfe17505baf3db50ebb9b97290bae.zip |
rust: error: allow specifying error type on `Result`
Currently, if the `kernel::error::Result` type is in scope (which is
often is, since it's in the kernel's prelude), you cannot write
`Result<T, SomeOtherErrorType>` when you want to use a different error
type than `kernel::error::Error`.
To solve this we change the error type from being hard-coded to just
being a default generic parameter. This still lets you write `Result<T>`
when you just want to use the `Error` error type, but also lets you
write `Result<T, SomeOtherErrorType>` when necessary.
Signed-off-by: Alice Ryhl <aliceryhl@google.com>
Reviewed-by: Benno Lossin <benno.lossin@proton.me>
Reviewed-by: Asahi Lina <lina@asahilina.net>
Reviewed-by: Andreas Hindborg <a.hindborg@samsung.com>
Reviewed-by: Gary Guo <gary@garyguo.net>
Link: https://lore.kernel.org/r/20230502124015.356001-1-aliceryhl@google.com
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions