From: "Jesung Yang" <y.j3ms.n@gmail.com>
To: "Tamir Duberstein" <tamird@gmail.com>, <y.j3ms.n@gmail.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] rust: take advantage of newer rust-analyzer features
Date: Wed, 04 Mar 2026 18:52:55 +0900 [thread overview]
Message-ID: <DGTWMO57AFUE.22DFGS0HKH2BO@gmail.com> (raw)
In-Reply-To: <CAJ-ks9nd4Vmbgw8gOajhU7ijgVrvcqpQL46rgX-tuPN1QOQBVg@mail.gmail.com>
On Tue Mar 3, 2026 at 1:58 AM KST, Tamir Duberstein wrote:
[...]
>
> Hi Jesung, is this something you'd be interested in updating now that
> type hints have been staged in rust-analyzer-next?
Yeah, I'll send the next version within a few days.
Best regards,
Jesung
prev parent reply other threads:[~2026-03-04 9:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 22:08 [PATCH v2 0/2] rust: take advantage of newer rust-analyzer features Jesung Yang
2026-01-09 22:08 ` Jesung Yang via B4 Relay
2026-01-09 22:09 ` [PATCH v2 1/2] scripts: generate_rust_analyzer: add versioning infrastructure Jesung Yang
2026-01-09 22:09 ` Jesung Yang via B4 Relay
2026-01-09 23:07 ` Tamir Duberstein
2026-01-11 1:21 ` Jesung Yang
2026-01-11 2:24 ` Gary Guo
2026-01-09 22:09 ` [PATCH v2 2/2] scripts: generate_rust_analyzer: fix IDE support for primitive types Jesung Yang
2026-01-09 22:09 ` Jesung Yang via B4 Relay
2026-03-02 16:58 ` [PATCH v2 0/2] rust: take advantage of newer rust-analyzer features Tamir Duberstein
2026-03-04 9:52 ` Jesung Yang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DGTWMO57AFUE.22DFGS0HKH2BO@gmail.com \
--to=y.j3ms.n@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@gmail.com \
--cc=tmgross@umich.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.