Re: [PATCH v3] rust: num: bounded: mark __new as unsafe

[Alexandre Courbot]

On Thu Dec 4, 2025 at 11:28 PM JST, Miguel Ojeda wrote:
> On Thu, Dec 4, 2025 at 3:13 PM Alexandre Courbot <acourbot@xxxxxxxxxx> wrote:
>>
>> Miguel, do you prefer to take this directly, or should I gather all the
>> `num/*` patches and send you a PR in one go sometime later?
>
> Just to avoid forgetting later, which ones do you mean? i.e. I have
> these in my radar:
>
>     [PATCH v3] rust: num: bounded: mark __new as unsafe
>     [PATCH] rust: num: fix typos in Bounded documentation
>     [PATCH] rust: num: bounded: rename `try_into_bitint` to `try_into_bounded`
>     One in [PATCH v2 0/7] rust: build_assert: document and fix use
> with function arguments
>
> None seems urgent, i.e. they can be added to `rust-fixes` after -rc1 I
> think, right?

Oh yes, actually I was thinking about rust-next rather than rust-fixes,
but that works as well. My point was more about taking the mental burden
of tracking this off your shoulders. :)