No description
Find a file
Daniel Baumann eac3e58411
Releasing fastforward version 1.0.228-2~ffwd13+u1.
Signed-off-by: Daniel Baumann <daniel@debian.org>
2025-12-29 12:55:30 +01:00
debian Releasing fastforward version 1.0.228-2~ffwd13+u1. 2025-12-29 12:55:30 +01:00
src Merging upstream version 1.0.228. 2025-12-29 12:54:26 +01:00
.cargo_vcs_info.json Merging upstream version 1.0.228. 2025-12-29 12:54:26 +01:00
build.rs Merging upstream version 1.0.228. 2025-12-29 12:54:26 +01:00
Cargo.lock Merging upstream version 1.0.228. 2025-12-29 12:54:26 +01:00
Cargo.toml Merging upstream version 1.0.228. 2025-12-29 12:54:26 +01:00
Cargo.toml.orig Merging upstream version 1.0.228. 2025-12-29 12:54:26 +01:00
LICENSE-APACHE Adding upstream version 1.0.226. 2025-12-29 12:54:07 +01:00
LICENSE-MIT Adding upstream version 1.0.226. 2025-12-29 12:54:07 +01:00
README.md Adding upstream version 1.0.226. 2025-12-29 12:54:07 +01:00

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