Michael Müller

Thanks for the example. SemanticDiff already ignores reordering of keys, but that doesn't help in this case because the elements within an array change their order. We obviously cannot add...

Manually writing the rules for all 333 schemas is not feasible, but it should be possible to write a script that extracts the location of all arrays. This still requires...

@MiguelElGallo We took a quick look and found that the schema contains a lot of `oneOf` entries. They complicate things because SemanticDiff needs to distinguish the object type in order...

@MiguelElGallo Sorry for not posting an update. We took a closer look at the idea a few weeks ago. During our analysis we found two problems: 1. The schema uses...

Our build pipeline does not yet support Windows ARM builds. Some of the SemanticDiff components are written in C++ and we use clang to compile for all platforms (Linux/macOS/Windows). Unfortunately,...

SemanticDiff already supports Rust. You can test it, for example, with this [commit](https://app.semanticdiff.com/gh/tensorzero/tensorzero/commit/19d04d76774f2cf172a0e98584aab2b615a80e7e#tensorzero-core/src/variant/best_of_n_sampling.rs?ignore_comments=false). SemanticDiff may not be able to handle all rust files yet, since we mostly focus on stable...

An AST is technically not sufficient for adding support for a new language / file format in SemanticDiff. ASTs often store information in an abstract format (e.g. a boolean to...

We are currently extending the SemanticDiff GitHub App with additional diff modes. This includes a word diff and should make it easier to review text even if the format is...

We already have an issue for XML support but it was always a bit unclear whether generic XML support would be useful. The spec does not really define when two...

Duplicate of #18