linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alice Ryhl <alice@ryhl.io>
To: John Hubbard <jhubbard@nvidia.com>, Alice Ryhl <aliceryhl@google.com>
Cc: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.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 21:49:17 +0200	[thread overview]
Message-ID: <d9b79f25-ae52-4cda-86d0-d4cde9338644@ryhl.io> (raw)
In-Reply-To: <7d708e79-1a94-499e-a0e8-c3431aeaea3d@nvidia.com>

On 10/21/24 9:34 PM, John Hubbard wrote:
> On 10/21/24 12:26 PM, Alice Ryhl wrote:
>> On Mon, Oct 21, 2024 at 9:09 PM John Hubbard <jhubbard@nvidia.com> wrote:
>>>
>>> On 10/21/24 11:59 AM, Alice Ryhl wrote:
>>>> 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.
>>>>
>>>
>>> Good question. I've never attempted that when discussing programming
>>> language details, because it hasn't come up, because it would be a
>>> programming error in C to use one in place of the other. And it is
>>> rare to refer to both cases in C.
>>>
>>> Rust so far seems to have the same distinction, although I am standing
>>> by to be corrected as necessary, there! :)
>>>
>>> At a higher level of abstraction, though, perhaps "grouping" is a good
>>> word.
>>
>> Rust macros can use different types of brackets. For example, the
>> `assert!(1 < 2)` macro uses round parenthesises, the `vec![1,2,3]`
>> macro uses square parenthesises, and the `thread_local! { ... }` macro
>> uses curly parenthesies. The round and square brackets are used for
>> expression-like things, and the curlies are used for things that
>> expand to top-level items such as global variables or functions.
>>
>> Macros cannot use any other delimiter than those three. So e.g. <>
>> wouldn't work.
> 
> That answers my implicit "are there any cases in which you would
> want to collectively refer to all three types of...bracket?", yes.
> 
> For the original point, though, we are not in a Rust macro. Is it
> actually allowable to use [] or {} here:
> 
> +    // Brackets around PAGE_SIZE-1 to avoid triggering overflow 
> sanitizers in the wrong cases.
> +    (addr + (PAGE_SIZE - 1)) & PAGE_MASK
> 
> ? Is that why you were not seeing a difference between saying "brackets"
> vs. "parentheses" there? If so, this would be yet another case of my
> Rust newbie-ness being inflicted on you. :)
You can use both () and {}, but you can only use brackets if you're 
European. ;)

Using {} to create a block works because a block evaluates to the value 
of the last expression in the block. It would be super weird to define a 
block here, though.

Alice


  reply	other threads:[~2024-10-21 19:46 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
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 [this message]
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=d9b79f25-ae52-4cda-86d0-d4cde9338644@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