rust-lang / rust-lang/rustfmt

Sort mods grouped by visibility

Open
#4,799 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-feature-request
Dominant language
Rust
Stars
7k
Forks
1.1k
Avg merge
2d 13h
Merged PRs (30d)
24

Description

📋 Description

Current behavior:

pub mod alpha;
mod beta;
pub(crate) mod gamma;
mod tau;
pub mod upsilon;

which is a mess and hard to read.

Feature request:

// pub (visible to all) first
pub mod alpha;
pub mod upsilon;

// then pub(crate) and other specifiers: pub(super), pub(in path), etc
pub(crate) mod gamma;

// private modules at the end
mod beta;
mod tau;

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue provides before-and-after Rust module declarations but names no files, tests, or entry points. Start by locating rustfmt's existing module-sorting behavior and determine how visibility specifiers are represented; done means public modules come first, followed by restricted visibility and private modules, while preserving alphabetical order within groups.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.