[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72nvkA-SS0_tUNX_Dv5ABXiA9aHf2NqNZMtxMOJgBEVuRw@mail.gmail.com>
Date: Fri, 2 Jan 2026 11:56:16 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Gary Guo <gary@...yguo.net>
Cc: Jesung Yang <y.j3ms.n@...il.com>,
Jesung Yang via B4 Relay <devnull+y.j3ms.n.gmail.com@...nel.org>, Miguel Ojeda <ojeda@...nel.org>,
Boqun Feng <boqun.feng@...il.com>, Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <lossin@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
Danilo Krummrich <dakr@...nel.org>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] scripts: generate_rust_analyzer: reduce the output file size
On Fri, Jan 2, 2026 at 11:36 AM Gary Guo <gary@...yguo.net> wrote:
>
> So I'd say while your change is desired, we need to wait until we bump
> MSRV to a high enough version as I suspect there're a lot more developers
> that use Rust analyzer in the same way I do.
Yeah, distributions likely provide the rust-analyzer that works well
with their `rustc`, thus older ones in some cases.
Perhaps we should support several versions, just like for the rest of
the toolchain, i.e. query the version in the Python script and act
based on that.
Cheers,
Miguel
Powered by blists - more mailing lists