chore: minor improvement for docs

Signed-off-by: claudecodering <claudecoder@outlook.com>
This commit is contained in:
claudecodering 2025-11-04 16:14:40 +08:00
parent ce410dd779
commit 250dc8a37b
3 changed files with 3 additions and 3 deletions

View File

@ -319,7 +319,7 @@ V>`, as well as any structs or enums annotated with `#[derive(Serialize)]`.
It is fast. You should expect in the ballpark of 500 to 1000 megabytes per
second deserialization and 600 to 900 megabytes per second serialization,
depending on the characteristics of your data. This is competitive with the
fastest C and C++ JSON libraries or even 30% faster for many use cases.
fastest C and C++ JSON libraries, or even 30% faster for many use cases.
Benchmarks live in the [serde-rs/json-benchmark] repo.
[serde-rs/json-benchmark]: https://github.com/serde-rs/json-benchmark

View File

@ -1,4 +1,4 @@
// The code in this module is derived from the `lexical` crate by @Alexhuszagh
// The code in this module is derived from the `lexical` crate by @Alexhuszagh,
// which the author condensed into this minimal subset for use in serde_json.
// For the serde_json use case we care more about reliably round tripping all
// possible floating point values than about parsing any arbitrarily long string

View File

@ -18,7 +18,7 @@
///
/// Variables or expressions can be interpolated into the JSON literal. Any type
/// interpolated into an array element or object value must implement Serde's
/// `Serialize` trait, while any type interpolated into a object key must
/// `Serialize` trait, while any type interpolated into an object key must
/// implement `Into<String>`. If the `Serialize` implementation of the
/// interpolated type decides to fail, or if the interpolated type contains a
/// map with non-string keys, the `json!` macro will panic.