diff options
| author | Matthias Krüger <476013+matthiaskrgr@users.noreply.github.com> | 2025-03-22 11:59:19 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-03-22 11:59:19 +0100 |
| commit | a4c0173d122a9272b4184b995b82fdbc96dcabab (patch) | |
| tree | 3dbf97d4807e1d72b63edca9f6739e2666de6b92 /compiler/rustc_pattern_analysis/src | |
| parent | fb09bd52a8b5a063f36aa840a42e7905a4d7ace7 (diff) | |
| parent | 13335e313c96fecd30e4ec28dececda046b6304b (diff) | |
| download | rust-a4c0173d122a9272b4184b995b82fdbc96dcabab.tar.gz rust-a4c0173d122a9272b4184b995b82fdbc96dcabab.zip | |
Rollup merge of #138763 - aDotInTheVoid:two-years-later, r=GuillaumeGomez
jsondocck: Replace `jsonpath_lib` with `jsonpath-rust` The current jsonpath implementation we use isn't spec-compliant, and is buggy. See https://github.com/freestrings/jsonpath/issues/91 To solve it, it's replaced with https://github.com/besok/jsonpath-rust. This is spec-compiant, and doesn't have a really awkward bug we need to always dance around. Unfortunately, this requires rewriting almost every test, as the behaviour of `[?(```@`,``` which is *extremely* common was changed. (But the new behaviour makes way more sense, and isn't buggy with tripply nested selectors) Unblocks #110406. Makes #100515 much easier as we don't need to explain the broken JSONPath implementation Best reviewed commit-by-commit. The first does the replacement. The next two rewrite the test-suite mechanically. The last rewrites the test-suite by hand. r? ```@GuillaumeGomez```
Diffstat (limited to 'compiler/rustc_pattern_analysis/src')
0 files changed, 0 insertions, 0 deletions
