-
Updated
Aug 12, 2021 - Python
serde
Here are 197 public repositories matching this topic...
-
Updated
Aug 10, 2021 - Rust
-
Updated
Jun 26, 2021 - Rust
From our benchmarks we can see that we are consistently slower than everyone else when serializing/deserializing boolean values. We should fix that.
orjson is using an unsafe block to create a reference to a boolean:
https://github.com/ijl/orjson/blob/03d55e99a953ce93cedc05f03e4b63b0bcbbcc7a/src/decode.rs#L81-L96
This avoids additional allocations.
For comparison, this is our code at the
-
Updated
Aug 12, 2021 - Rust
#[serde_with::serde_as]
#[derive(Debug, serde::Deserialize)]
struct FooBar(#[serde_as(as = "VecSkipError<_>")] Vec<u32>);
serde_json::from_value::<FooBar>(serde_json::json!([
0,
"String",
1,
[],
2,
{},
3,
]))?
// Results in
// FooBar([0, 1, 2, 3])VecSkipError implementation
str-
Updated
Jun 26, 2021 - Rust
-
Updated
Aug 10, 2021 - Rust
We get the return annotation for free, so we should allow users to do something with it.
-
Updated
Aug 6, 2021 - Scala
-
Updated
Jul 12, 2021 - Rust
We could use https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows#schedule to look for changes in the go sdk and automatically put up a PR.
-
Updated
Aug 12, 2021 - Java
-
Updated
Jan 17, 2021 - Rust
-
Updated
Feb 10, 2021 - Python
Improve this page
Add a description, image, and links to the serde topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the serde topic, visit your repo's landing page and select "manage topics."
In the following string validation, the error message points to the close quote after "test123". It would be nicer to point to the opening quote instead.