EXPORTED_PRIVATE_DEPENDENCIES in rustc_lint::builtin - Rust
Description: The `exported_private_dependencies` lint detects private dependencies that are exposed in a public interface.

Skip to main content

## EXPORTED_PRIVATE_DEPENDENCIES

# Static EXPORTED_PRIVATE_DEPENDENCIES

Source

    pub static EXPORTED_PRIVATE_DEPENDENCIES: &'static Lint

Expand description

The `exported_private_dependencies` lint detects private dependencies that are exposed in a public interface.

#### §Example

ⓘ

    pub fn foo() -> Option<some_private_dependency::Thing> {
        None
    }

This will produce:

    warning: type `bar::Thing` from private dependency 'bar' in public interface
     --> src/lib.rs:3:1
      |
    3 | pub fn foo() -> Option<bar::Thing> {
      | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      |
      = note: `#[warn(exported_private_dependencies)]` on by default

#### §Explanation

Dependencies can be marked as “private” to indicate that they are not exposed in the public interface of a crate. This can be used by Cargo to independently resolve those dependencies because it can assume it does not need to unify them with other packages using that same dependency. This lint is an indication of a violation of that contract.

To fix this, avoid exposing the dependency in your public interface. Or, switch the dependency to a public dependency.

Note that support for this is only available on the nightly channel. See RFC 1977 for more details, as well as the Cargo documentation.