serde_test should be dev-dependency

[Mingun]

If I'm not missing something, it is required only for tests, so it should be in the [dev-dependencies] section

[tormol]

serde is an optional dependency, so how does one add a feature-specific dev-dependency?

I tried

[target.'cfg(feature="serde")'.dev-dependencies]
serde_test = "1.0"

but cargo warns that it doesn't work as expected, and extern crate serde_test; fails. (With and without resolver = "2").

Is it the norm to require all features to build tests?

(I've also asked about this in an r/rust questions thread, but since this isn't the only project with optional serde support you've opened an issue for, I guess you know.)

[tormol]

Based on your comment on circular-queue I tried just doing

[dev-dependencies]
serde_test = "1.0"

but when I run cargo build --no-default-features --tests I get

   Compiling serde v1.0.163
   Compiling serde_test v1.0.163
   Compiling ascii v1.1.0 (/home/tbm/p/rust/libs/ascii)
    Finished dev [unoptimized + debuginfo] target(s) in 1.93s

even though serde was not enabled.
so what you said about the serde_test dependency not being compiled appears not to be the case.

[Mingun]

Hm, I tried to provide compilation of quick-xml which have only one required dependency, but cargo test --no-default-features builds all libraries listed in [dev-dependencies] section, even unused for the selected test options (for example, tokio-test which needed only when enabling async-tokio feature). So it seems that my assumption is wrong and I observed some other effect that reduced number of used libraries.