Skip to content

Commit 8aabb1b

Browse files
committed
docs(gctx): move rationale to rationale paragraph
1 parent 6b40446 commit 8aabb1b

File tree

1 file changed

+1
-8
lines changed

1 file changed

+1
-8
lines changed

src/cargo/util/context/value.rs

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -9,19 +9,12 @@
99
//! from configuration, but also record where it was deserialized from when it
1010
//! was read.
1111
//!
12-
//! ## How `Value<T>` deserialization works
13-
//!
1412
//! Deserializing `Value<T>` is pretty special, and serde doesn't have built-in
1513
//! support for this operation. To implement this we extend serde's "data model"
1614
//! a bit. We configure deserialization of `Value<T>` to basically only work with
1715
//! our one deserializer using configuration.
1816
//!
19-
//! We define that `Value<T>` deserialization asks the deserializer for a very
20-
//! special [struct name](NAME) and [struct field names](FIELDS). In doing so,
21-
//! the deserializer will recognize this and synthesize a magical value for the
22-
//! `definition` field when we deserialize it. This protocol is how we're able
23-
//! to have a channel of information flowing from the configuration deserializer
24-
//! into the deserialization implementation here.
17+
//! ## How `Value<T>` deserialization works
2518
//!
2619
//! You'll want to also check out the implementation of `ValueDeserializer` in
2720
//! the [`de`] module. Also note that the names below are intended to be invalid

0 commit comments

Comments
 (0)