3 ms·
> In practice, once a codebase gets above a specific size, it becomes completely impossible to exclude any features in a crate's default list because `default-f
by matklad 5y ago
> In practice, once a codebase gets above a specific size, it becomes completely impossible to exclude any features in a crate's default list because `default-features=false` only applies locally
Curious, what that specific size approximately is? For rust-analyzer, getting all the deps to use features correctly is rather annoying, but isn’t particularly time-consuming.
- stormbrew 5y agoI think we must be talking about different things because rust-analyzer doesn't enter into or help the issue I'm talking about? If you depend on crates A and B, and B depends on A, and you specify `default-features=false` on A but B doesn't, you will always get A's default features included in your compile. There is no way to prevent this.