`include_str` or `include_bytes` not in `Cargo.toml/include`

What it does

Checks paths in include_str and include_bytes and make sure those paths are found in the include field in Cargo.toml.

Advantage

When using a workspace it is easy to make the mistake of include_bytes!("../../other_crate/data/file.png"). The code will run, but cargo publish will fail, as the referenced file is not part of the crate.

This is true for any file not found in the include field of the crate's Cargo.toml.

Drawbacks

This is only relevant for crates that are intended to be published, i.e. has publish = true in their Cargo.toml.

Example

include_bytes!("../../other_crate/data/file.png")

Clippy warning: The file "../../other_crate/data/file.png" is outside the this crate, so cargo publish will fail.

Start by examining how Rust Clippy implements lints that inspect macros and crate metadata, then review the issue's include_str!/include_bytes! example and Cargo.toml include behavior. Done means identifying publishable crates, checking referenced paths against the crate's include field, and reporting the proposed warning without affecting unpublished crates.