[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72mY97PXbEev1b-ZO=RV-oeAR8Hr6W4v8ndZuegByqz0jA@mail.gmail.com>
Date: Sun, 4 Dec 2022 01:58:15 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Josh Triplett <josh@...htriplett.org>
Cc: ojeda@...nel.org, Wedson Almeida Filho <wedsonaf@...il.com>,
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>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
patches@...ts.linux.dev, Wei Liu <wei.liu@...nel.org>
Subject: Re: [PATCH v2 27/28] rust: types: add `Either` type
On Sat, Dec 3, 2022 at 12:42 AM Josh Triplett <josh@...htriplett.org> wrote:
>
> This specific example seems like it would be better served by the
> existing `Cow` type.
Yeah, possibly -- it is taken from one of the use cases in the full
repository. Perhaps it was deemed simpler, or providing a way to go to
an owned instance was to be avoided.
Thanks for taking a look!
Cheers,
Miguel
Powered by blists - more mailing lists