rust-lang / rust-lang/rust

Tracking Issue for default-visibility

Open
#131,090 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-tracking-issue
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

This is a tracking issue for default-visibility, which allows setting the visibility of symbols when building a shared object / dylib.

MCP: https://github.com/rust-lang/compiler-team/issues/782

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Steps
  • Implement the flag as -Z default-visibility
  • Stabilize as -C default-visibility
Unresolved Questions
  • Are we happy with the naming of the flag and its options?
  • What should the default be?
Implementation history

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

Start with the MCP at compiler-team issue 782 and the implementation history in rust-lang/rust#130005. Review the tracking checklist and unresolved questions before deciding on work. Done means implementing -Z default-visibility, stabilizing it as -C default-visibility, and resolving the naming and default-value questions.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
build-system, compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.