Skip to content

[pull] master from rust-lang:master#102

Merged
pull[bot] merged 3 commits into
Arstman:masterfrom
rust-lang:master
Apr 7, 2026
Merged

[pull] master from rust-lang:master#102
pull[bot] merged 3 commits into
Arstman:masterfrom
rust-lang:master

Conversation

@pull

@pull pull Bot commented Apr 7, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

traviscross and others added 3 commits April 4, 2026 20:51
*Usage* means a customary pattern of use (as in "regional usage
varies") or a rate or quantity of use (as in "disk usage").  It
doesn't mean *use*.  Whenever *use* works, *usage* shouldn't appear.

Let's fix each incorrect use of *usage* -- i.e., adopt better *usage*
of *usage* -- throughout the prose of the Reference.
In the prior commit, we fixed prose occurrences of *usage*.  The same
reasoning applies to the rule identifiers.

These rules describe where the language permits a construct to appear.
On the surface, that may seem to be a kind of pattern of use, but it's
not (in the sense implied by *usage*), and ultimately *use* is still
the right word.  The word *usage* describes conventions and customs --
i.e., *customary* patterns of use.  It describes how a community uses
something and how that varies, e.g., across regions.

That's not what we're doing here.  We're not describing better or
worse Rust idioms.  There's no "nonstandard usage" of Rust grammatical
constructs -- that's not what we're defining, at least.

Let's fix each rule identifier to use `use` instead.

(None of these identifiers were referenced elsewhere in
the Reference.)
Fix misuse of *usage* throughout the Reference
@pull pull Bot locked and limited conversation to collaborators Apr 7, 2026
@pull pull Bot added the ⤵️ pull label Apr 7, 2026
@pull pull Bot merged commit 6d20724 into Arstman:master Apr 7, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants