[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72mq0KYXSLVSG7uR=L_TGeqnrfkj1PqaFbMOxy6qjwqfmA@mail.gmail.com>
Date: Mon, 21 Jul 2025 23:58:55 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Benno Lossin <lossin@...nel.org>
Cc: Alice Ryhl <aliceryhl@...gle.com>, Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>, Boqun Feng <boqun.feng@...il.com>,
Gary Guo <gary@...yguo.net>, Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>, Andreas Hindborg <a.hindborg@...nel.org>,
Trevor Gross <tmgross@...ch.edu>, Danilo Krummrich <dakr@...nel.org>, Tamir Duberstein <tamird@...il.com>,
Dirk Behme <dirk.behme@...bosch.com>, Kartik Prajapati <kartikprajapati987@...il.com>,
Aliet Exposito Garcia <aliet.exposito@...il.com>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rust: types: remove `Either<L, R>`
On Mon, May 19, 2025 at 8:23 PM Benno Lossin <lossin@...nel.org> wrote:
>
> Another option would be to deprecate it. Do I remember correctly that
> Linus doesn't like that? If yes, then that maybe isn't a good idea...
Yeah, though for Rust we may need it sometimes during the "phased"
moves of items between Rust modules.
In this case, it is just not used upstream, and the only user
out-of-tree is easy to replace, so there is nothing stopping us from
just removing it.
Cheers,
Miguel
Powered by blists - more mailing lists