Rust-GCC / Rust-GCC/gccrs

private function in an imported file should give an error not a warning

Open
#4,259 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
2.9k
Forks
231
Avg merge
19h 55m
Merged PRs (30d)
67

Description

code:
main.rs

mod b;
use b::b;
fn main(){}

b.rs:

fn b(){}

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 by compiling the supplied main.rs and b.rs example and compare the diagnostic for the private imported function. Trace the Rust name-resolution or visibility diagnostic path responsible for turning this case into a warning. Done means the example reports an error for importing b::b from the private function in b.rs.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.