Code that is only used in test cases can be put behind #[cfg(test)].

[squell]

What the title says. I thought this would show up but in a test I'm running it didn't.

[squell]

Sorry, this only happened in a binding I was looking at where pub was used.

Confirmed; I think code that is only used in test cases should at the very least be behind a #[cfg(test)] protection. We could add a flag that adds these to the code (removing test-cases is perhaps not the best idea...)

[squell]

Example:

const X: usize = 0;
const Y: usize = 0;

#[test]
fn test() {
    let _ = Y;
}
fn main() {
    println!("Hello, world!");
}

A cargo minify will only remove X, not Y; I would expect a diagnostic that this code can be transformed into:

#[cfg(test)]
const Y: usize = 0;

#[test]
fn test() {
    let _ = Y;
}
fn main() {
    println!("Hello, world!");
}

[squell]

Another use case:

fn main() {
    println!("Hello, world!");
}

fn bar() -> bool {
    true
}

#[cfg(test)]
mod test {
    use super::*;

    #[test]
    fn foo() {
	assert!(bar());
    }
}

[van-sprundel]

This could be split into two features. One would be to check if it's only used in a test environment, and the other if it's only used inside a specific module (since it doesn't have to specifically be a test module). Am I getting that right?