From: Danilo Krummrich <dakr@redhat.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Alice Ryhl <aliceryhl@google.com>,
a.hindborg@samsung.com, alex.gaynor@gmail.com,
benno.lossin@proton.me, bjorn3_gh@protonmail.com,
boqun.feng@gmail.com, gary@garyguo.net,
linux-kernel@vger.kernel.org, ojeda@kernel.org,
rust-for-linux@vger.kernel.org, wedsonaf@gmail.com
Subject: Re: [PATCH v4] rust: str: add {make,to}_{upper,lower}case() to CString
Date: Tue, 20 Feb 2024 20:55:52 +0100 [thread overview]
Message-ID: <e8b4cb98-b0ab-4754-b80a-9df77983137a@redhat.com> (raw)
In-Reply-To: <CANiq72m7-5CuKAKDk=G9sauri_sH0nR2TXi8ye5Eji-qaum3sw@mail.gmail.com>
On 2/20/24 17:53, Miguel Ojeda wrote:
> On Tue, Feb 20, 2024 at 4:53 PM Danilo Krummrich <dakr@redhat.com> wrote:
>>
>> The rational for a convention can't be that it is a convention. Instead
>> it should be a convention for an objective reason.
>
> The rationale __for the lint__ is that it is a very established
> convention in Rust code.
Understood. I'm basically just asking why this is the convention.
Because I assume that there must be a good reason for that. If there is none,
and it's really just because everyone is doing it, I personally think that's
not an objective rationale.
If there is no other reason it could even be just the opposite causality, as in
it became the convention because clippy enforces it. (Disclaimer: I really don't
know and so far I have no reason to assume so.)
Generally, I don't think there is anything wrong with questioning things and I
also don't think there is anything wrong in not accepting "because everyone does
so" as an objective rationale.
Otherwise I don't see any disagreement. I also understood that you want to be
consistent and comply with this convention and surely I accept that.
But again, I also think it's perfectly valid questioning things.
>
> That is what Clippy is telling you.
>
> You may not agree with the convention (and thus the lint). That is
> fine, but it is still a fact that it is the convention, and that is
> why I said whoever wrote that Clippy description probably felt that
> wording is good enough.
>
>> I'm not saying that we should enforce it otherwise, I just think that we
>> should have objective reasons for restrictions.
>
> Again, you seem to be saying we do not have objective reasons.
I'm honestly sorry about this misunderstanding and that this seems to be an
emotional discussion for you.
I never said that you don't have objective reasons (in general). I just said that
I don't consider *one specific rationale* as objective (or factual).
And I think it's perfectly valid to claim the right to do so. This isn't a personal
attack in any way.
prev parent reply other threads:[~2024-02-20 19:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 16:39 [PATCH v4] rust: str: add {make,to}_{upper,lower}case() to CString Danilo Krummrich
2024-02-20 9:35 ` Alice Ryhl
2024-02-20 12:02 ` Danilo Krummrich
2024-02-20 13:17 ` Alice Ryhl
2024-02-20 14:53 ` Danilo Krummrich
2024-02-20 15:45 ` Miguel Ojeda
2024-02-20 19:55 ` Danilo Krummrich
2024-02-20 15:04 ` Miguel Ojeda
2024-02-20 15:53 ` Danilo Krummrich
2024-02-20 16:53 ` Miguel Ojeda
2024-02-20 19:55 ` Danilo Krummrich [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=e8b4cb98-b0ab-4754-b80a-9df77983137a@redhat.com \
--to=dakr@redhat.com \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).