[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAA76j92DXbCrMoW1sta32TS5nnbTrgyXoOH=twwFeO1bzo-gSA@mail.gmail.com>
Date: Wed, 19 Feb 2025 21:11:37 +0100
From: Sergio González Collado <sergio.collado@...il.com>
To: Alexandre Courbot <acourbot@...dia.com>
Cc: Timur Tabi <ttabi@...dia.com>,
"daniel.almeida@...labora.com" <daniel.almeida@...labora.com>, John Hubbard <jhubbard@...dia.com>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"rust-for-linux@...r.kernel.org" <rust-for-linux@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"nouveau@...ts.freedesktop.org" <nouveau@...ts.freedesktop.org>, "dakr@...nel.org" <dakr@...nel.org>,
"airlied@...il.com" <airlied@...il.com>, Ben Skeggs <bskeggs@...dia.com>
Subject: Re: [PATCH RFC 1/3] rust: add useful ops for u64
> Actually. How about adding methods to this trait that return either
> component?
>
> let some_u32 = some_u64.high_half();
> let another_u32 = some_u64.low_half();
>
> These should be used most of the times, and using destructuring/tuple
> would only be useful for a few select cases.
>
Indeed very nice!
Powered by blists - more mailing lists