rust-lang / rust-lang/rust-clippy

New Lint: Unnameable type in public API

Open
#3,618 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-lint
Dominant language
Rust
Stars
13.5k
Forks
2.2k
Avg merge
2d 10h
Merged PRs (30d)
32

Description

a.k.a. an enhanced private-in-public lint.

For example this currently compiles without warning, even though users of the library cannot name the return type of foo (playground):

use self::foo::Foo;

mod foo { pub struct Foo; }

pub fn foo() -> Foo {
    Foo
}

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 no file or test path. Start by reproducing the Rust example and locating the existing private-in-public lint; done means reporting public APIs whose exposed types users cannot name.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.