diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2025-01-25 08:03:38 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-01-25 08:03:38 +0100 |
| commit | a330c7ee858a03dacaf10a7f88abb38eb4f1858a (patch) | |
| tree | 8dd95154108c79d6d6ab2ac45bc19a6f9b8b6662 /compiler/rustc_data_structures/src | |
| parent | 7b16b4e4cb9ab3ebc3653d4257dd38c48c20c5a6 (diff) | |
| parent | 5f8bcec6c8e006f0b73b9bff076299f77d6c166c (diff) | |
| download | rust-a330c7ee858a03dacaf10a7f88abb38eb4f1858a.tar.gz rust-a330c7ee858a03dacaf10a7f88abb38eb4f1858a.zip | |
Rollup merge of #136034 - weihanglo:null-as-f64-nan, r=compiler-errors
fix(bootstrap): deserialize null as `f64::NAN` When doing optimized build through opt-dist, I've often run into errors like `invalid type: null, expected f64`. This is likely because some f64 fields might actually bet set null. Unfortunately, serde_json doesn't handle null <-> NaN well. This commit addresses it by having a custom deserialize method, so null is always be deserialized to `f64:NAN`. See: * https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/opt-dist.3A.20.60invalid.20type.3A.20null.2C.20expect.20f64.60.20failure * https://github.com/serde-rs/json/issues/202 r? `@Kobzol`
Diffstat (limited to 'compiler/rustc_data_structures/src')
0 files changed, 0 insertions, 0 deletions