Skip to content

Conversation

@ehuss
Copy link
Contributor

@ehuss ehuss commented Jun 30, 2025

New rules:

  • names.preludes.no_implicit_prelude.syntax
  • names.preludes.no_implicit_prelude.allowed-positions
  • names.preludes.no_implicit_prelude.duplicates
  • names.preludes.no_implicit_prelude.excluded-preludes

@rustbot rustbot added the S-waiting-on-review Status: The marked PR is awaiting review from a maintainer label Jun 30, 2025
@ehuss ehuss force-pushed the no_implicit_prelude branch from 19a6c42 to acd6d6d Compare September 22, 2025 20:33
@ehuss ehuss force-pushed the no_implicit_prelude branch from acd6d6d to 227819e Compare November 9, 2025 02:58
@rustbot

This comment has been minimized.

@ehuss ehuss force-pushed the no_implicit_prelude branch from 227819e to 20c562e Compare November 9, 2025 03:06
ehuss and others added 11 commits November 11, 2025 23:36
This is to follow the attribute template.
This rewrites the intro to be a little more general, and moves the
description of the behavior to a specific rule that can be cited.
More closely align with the template, and some minor word tweaks.
… text

This follows our style guide where the main text should document the
current edition, and the edition blocks should note the differences to
previous editions.
One of the comments in the example stretched out a bit far; let's wrap
that and reword the comments in the example for clarity and flow.
It's more clear to say either that something can be applied "at the
crate level" or "to the crate" than "to the crate level".  Let's pick
the latter and adjust for better grammatical parallelism.
Rather than saying "or any of its descendants", we can say "and its
descendants" to express the same thing more concisely.  Let's do that.
The remainder of this note is in the present tense, so saying that
something "will" happen starting in the 2018 edition makes it sound as
though that will happen in the future, even if what we mean is that
the compiler "will" do it in the 2018 edition and later.  Let's use
the present tense here in emphatic form to distinguish this, and let's
expand "it" for clarity.
@rustbot
Copy link
Collaborator

rustbot commented Nov 11, 2025

This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

@traviscross traviscross added this pull request to the merge queue Nov 11, 2025
Merged via the queue into rust-lang:master with commit 3ba86bf Nov 11, 2025
5 checks passed
@rustbot rustbot removed the S-waiting-on-review Status: The marked PR is awaiting review from a maintainer label Nov 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants