mirror of
https://github.com/pezkuwichain/serde.git
synced 2026-04-24 23:57:57 +00:00
pezkuwichain
0a75fdd839
The redundant `use ::core::prelude::rust_2021::*;` was causing ambiguity errors because `crate::lib::*` already imports `Some`, `None`, `Option` via `crate_root.rs`. This fixes cargo clippy/check failures on wasm32 targets. Files fixed: - serde_core/src/de/mod.rs - serde_core/src/de/impls.rs - serde_core/src/ser/mod.rs - serde_core/src/ser/impls.rs - serde_core/src/ser/fmt.rs - serde_core/src/ser/impossible.rs - serde_core/src/private/doc.rs
The serde_core crate contains Serde's trait definitions with no support for
#[derive()].
In crates that derive an implementation of Serialize or Deserialize, you
must depend on the serde crate, not serde_core.
In crates that handwrite implementations of Serde traits, or only use them as
trait bounds, depending on serde_core is permitted. But serde re-exports all
of these traits and can be used for this use case too. If in doubt, disregard
serde_core and always use serde.
Crates that depend on serde_core instead of serde are able to compile in
parallel with serde_derive even when serde's "derive" feature is turned on,
as shown in the following build timings.
When serde_json depends on serde |
|---|
When serde_json depends on serde_core |
|---|