[dev-dependencies.automod]
version = "0.1"
[dev-dependencies.rustversion]
version = "0.1"
[dev-dependencies.serde_bytes]
version = "0.11"
[dev-dependencies.serde_derive]
version = "1.0"
[dev-dependencies.serde_stacker]
version = "0.1"
[dev-dependencies.trybuild]
version = "1.0"
$ ls
Cargo.toml Cargo.toml.orig LICENSE-APACHE LICENSE-MIT README.md src
$ grep 'automod' -r .
./Cargo.toml.orig:automod = "0.1"
./Cargo.toml:[dev-dependencies.automod]
$ grep 'rustversion' -r .
./Cargo.toml.orig:rustversion = "0.1"
./Cargo.toml:[dev-dependencies.rustversion]
$ grep 'serde_bytes' -r .
./Cargo.toml.orig:serde_bytes = "0.11"
./src/de.rs: /// use serde_bytes::ByteBuf;
./src/de.rs: /// use serde_bytes::ByteBuf;
./Cargo.toml:[dev-dependencies.serde_bytes]
kent@katipo2 ~/.cpanm/work/1571714539.20228/serde_json-1.0.41 $ grep 'serde_derive' -r .
./Cargo.toml.orig:serde_derive = "1.0"
./Cargo.toml:[dev-dependencies.serde_derive]
kent@katipo2 ~/.cpanm/work/1571714539.20228/serde_json-1.0.41 $ grep 'serde_stacker' -r .
./Cargo.toml.orig:serde_stacker = "0.1"
./Cargo.toml.orig:# stack adapter provided by the serde_stacker crate. Additionally you will need
./src/de.rs: /// growing stack adapter provided by the serde_stacker crate. Additionally
./src/de.rs: /// let deserializer = serde_stacker::Deserializer::new(&mut deserializer);
./Cargo.toml:[dev-dependencies.serde_stacker]
$ grep 'trybuild' -r .
./Cargo.toml.orig:trybuild = "1.0"
./Cargo.toml:[dev-dependencies.trybuild]
This combination of choices is a waste of time for everyone who attempts to run tests on the shipped crate, and makes quality-assurance on published crates nigh impossible.
Granted, some of this exposes inadequacies in cargo, like:
Though currently, these tests are nothing more than an almost no-op
of "it compiles", as the entire test suite is stripped by upstream
during shipping, and subsequently, a whole bunch of unused
dev-dependencies are patched out to keep things simple.
Bug: serde-rs/json#578
Package-Manager: Portage-2.3.75, Repoman-2.3.16
Signed-off-by: Kent Fredric <kentnl@gentoo.org>
kentfredric
added a commit
to kentfredric/rust-dev-overlay
that referenced
this issue
Nov 19, 2019
Though currently, these tests are nothing more than an almost no-op
of "it compiles", as the entire test suite is stripped by upstream
during shipping, and subsequently, a whole bunch of unused
dev-dependencies are patched out to keep things simple.
Bug: serde-rs/json#578
Package-Manager: Portage-2.3.75, Repoman-2.3.16
Signed-off-by: Kent Fredric <kentnl@gentoo.org>
kentfredric
added a commit
to kentfredric/rust-dev-overlay
that referenced
this issue
Jan 6, 2020
Though currently, these tests are nothing more than an almost no-op
of "it compiles", as the entire test suite is stripped by upstream
during shipping, and subsequently, a whole bunch of unused
dev-dependencies are patched out to keep things simple.
Bug: serde-rs/json#578
Package-Manager: Portage-2.3.75, Repoman-2.3.16
Signed-off-by: Kent Fredric <kentnl@gentoo.org>
kentfredric commentedOct 22, 2019
This combination of choices is a waste of time for everyone who attempts to run tests on the shipped crate, and makes quality-assurance on published crates nigh impossible.
Granted, some of this exposes inadequacies in cargo, like:
But its presently a bug in the crate itself.
The text was updated successfully, but these errors were encountered: