From: Gary Guo <gary@garyguo.net>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: "Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Stephen Boyd" <swboyd@chromium.org>,
"Jean Delvare" <jdelvare@suse.de>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev
Subject: Re: [PATCH] .gitattributes: set diff driver for Rust source code files
Date: Wed, 19 Apr 2023 13:11:21 +0100 [thread overview]
Message-ID: <20230419131121.6f5f5acf.gary@garyguo.net> (raw)
In-Reply-To: <20230418233048.335281-1-ojeda@kernel.org>
On Wed, 19 Apr 2023 01:30:48 +0200
Miguel Ojeda <ojeda@kernel.org> wrote:
> Git supports a builtin Rust diff driver [1] since v2.23.0 (2019).
>
> It improves the choice of hunk headers in some cases, such as
> diffs within methods, since those are indented in Rust within
> an `impl` block, and therefore the default diff driver would
> pick the outer `impl` block instead (rather than the method
> where the changed code is).
>
> For instance, with the default diff driver:
>
> @@ -455,6 +455,8 @@ impl fmt::Write for RawFormatter {
> // Amount that we can copy. `saturating_sub` ensures we get 0 if `pos` goes past `end`.
> let len_to_copy = core::cmp::min(pos_new, self.end).saturating_sub(self.pos);
>
> + test_diff_driver();
> +
> if len_to_copy > 0 {
> // SAFETY: If `len_to_copy` is non-zero, then we know `pos` has not gone past `end`
> // yet, so it is valid for write per the type invariants.
>
> With the Rust diff driver:
>
> @@ -455,6 +455,8 @@ fn write_str(&mut self, s: &str) -> fmt::Result {
> // Amount that we can copy. `saturating_sub` ensures we get 0 if `pos` goes past `end`.
> let len_to_copy = core::cmp::min(pos_new, self.end).saturating_sub(self.pos);
>
> + test_diff_driver();
> +
> if len_to_copy > 0 {
> // SAFETY: If `len_to_copy` is non-zero, then we know `pos` has not gone past `end`
> // yet, so it is valid for write per the type invariants.
>
> Thus set the `rust` diff driver for `*.rs` source files.
>
> Link: https://git-scm.com/docs/gitattributes#_defining_a_custom_hunk_header [1]
> Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
This is also done in rustc repo:
https://github.com/rust-lang/rust/blob/master/.gitattributes
Reviewed-by: Gary Guo <gary@garyguo.net>
> ---
> .gitattributes | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/.gitattributes b/.gitattributes
> index c9ba5bfc4036..2325c529e185 100644
> --- a/.gitattributes
> +++ b/.gitattributes
> @@ -2,3 +2,4 @@
> *.[ch] diff=cpp
> *.dts diff=dts
> *.dts[io] diff=dts
> +*.rs diff=rust
>
> base-commit: 09a9639e56c01c7a00d6c0ca63f4c7c41abe075d
next prev parent reply other threads:[~2023-04-19 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 23:30 [PATCH] .gitattributes: set diff driver for Rust source code files Miguel Ojeda
2023-04-19 2:45 ` Martin Rodriguez Reboredo
2023-04-19 12:11 ` Gary Guo [this message]
2023-04-19 12:30 ` Benno Lossin
2023-05-31 17:03 ` Miguel Ojeda
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=20230419131121.6f5f5acf.gary@garyguo.net \
--to=gary@garyguo.net \
--cc=alex.gaynor@gmail.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=ojeda@kernel.org \
--cc=patches@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=swboyd@chromium.org \
--cc=wedsonaf@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox