Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Clarify M-SMALLER-CRATES is mostly orthogonal to whether users should see the smaller crates.

Open
#22 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
documentation

Research direction

Locate the guideline section discussing M-SMALLER-CRATES and read its surrounding guidance on crate visibility and re-exports. Clarify that the guideline is independent of whether users should interact with smaller crates, while preserving the umbrella-crate example. Done when the resulting wording states this distinction unambiguously; no test is mentioned.

Written by the indexing model from the issue text.

Description

issue

... in other words, it's perfectly normal in rust to have foo re-exporting foo_x and foo_y as an umbrella, and rightfully expecting that users will not deal with foo_x and foo_y directly (and if they do and run into issues, e.g., around macros) it's just a not supported use case).

Dominant language
Rust
Stars
206
Forks
25
Avg merge
6d 13h
Merged PRs (30d)
3

Getting set up

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.

More from microsoft/rust-guidelines

All issues in microsoft/rust-guidelines

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.