You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 25, 2024. It is now read-only.
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error("foo: invalid type: integer `7200`, expected u32", line: 3, column: 8)', main.rs:25:7
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
The text was updated successfully, but these errors were encountered:
silverjam
changed the title
Can't map for !!int tagged type to Rust type with serde_yaml 0.9
Can't map !!int tagged type to Rust type with serde_yaml 0.9
Sep 14, 2022
I've published a fix in 0.9.12. Please file other issues if you notice anything else going wrong with this safe_dump/default_style format. This corner of YAML is tricky to get right.
I've published a fix in 0.9.12. Please file other issues if you notice anything else going wrong with this safe_dump/default_style format. This corner of YAML is tricky to get right.
Wonderful, thank you!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In
serde_yaml
0.8 the following code is able to map from a!!int
tagged type to a Rustu32
:In serde_yaml 0.9 the following error occurs:
See gist here https://gist.github.com/silverjam/254c5b6ecd526726e17f89135710034e -- I've also tried other Rust datatypes like
i64
but to no avail.The text was updated successfully, but these errors were encountered: