From: Alice Ryhl <alice@ryhl.io>
To: John Hubbard <jhubbard@nvidia.com>,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Alice Ryhl" <aliceryhl@google.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
linux-mm@kvack.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] rust: page: add Rust version of PAGE_ALIGN
Date: Mon, 21 Oct 2024 20:59:13 +0200 [thread overview]
Message-ID: <afc139fe-ac03-43e7-a5c0-22410f1acea3@ryhl.io> (raw)
In-Reply-To: <b93805c1-28a6-4ad9-b0d2-5116ef4b0d83@nvidia.com>
On 10/21/24 8:41 PM, John Hubbard wrote:
> On 10/21/24 11:37 AM, Miguel Ojeda wrote:
>> On Mon, Oct 21, 2024 at 8:35 PM John Hubbard <jhubbard@nvidia.com> wrote:
>>>
>>> Is this another case of C and Rust using different words for things??
>>> Wow. OK...
>>
>> I am not sure what you mean -- by BE I meant British English.
>>
>> See my other reply as well -- I just changed it anyway because Rust
>> apparently uses "parentheses".
>>
>
> Right. For spoken languages, that's simply preference, and I would not
> try to impose anything on anyone there.
>
> But in this case, at least for C (and, from reading my Rust book(s), I
> thought for Rust also), "parentheses" is a technical specification, and
> we should prefer to be accurate:
>
> parentheses: ()
> brackets: []
>
> Yes?
What word would you use to collectively talk about (), [], {}? In my
native language they're all a kind of parenthesis.
Alice
next prev parent reply other threads:[~2024-10-21 18:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 11:34 Alice Ryhl
2024-10-21 18:13 ` Miguel Ojeda
2024-10-21 18:20 ` John Hubbard
2024-10-21 18:29 ` Miguel Ojeda
2024-10-21 18:34 ` John Hubbard
2024-10-21 18:37 ` Miguel Ojeda
2024-10-21 18:41 ` John Hubbard
2024-10-21 18:59 ` Alice Ryhl [this message]
2024-10-21 19:08 ` John Hubbard
2024-10-21 19:26 ` Alice Ryhl
2024-10-21 19:34 ` John Hubbard
2024-10-21 19:49 ` Alice Ryhl
2024-10-21 19:51 ` John Hubbard
2024-10-21 18:32 ` Alice Ryhl
2024-10-21 18:36 ` 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=afc139fe-ac03-43e7-a5c0-22410f1acea3@ryhl.io \
--to=alice@ryhl.io \
--cc=a.hindborg@kernel.org \
--cc=akpm@linux-foundation.org \
--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=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=willy@infradead.org \
/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