It was not immediately clear why the second `CrdsValue` insertion in the test must always succeed. Turns out the test was relying on hash values having a specific relationship. It is confusing to someone not deeply familiar with the test. As overwrite based on the hash value is not part of the behavior that we consider valuable, we just remove that check. Unified assertion between two checks into one. |
||
---|---|---|
.. | ||
benches | ||
src | ||
tests | ||
.gitignore | ||
Cargo.toml | ||
build.rs |