Use pretty-assertions and improve debug implementation of Key#19
Merged
lhemala merged 2 commits intolhemala:mainfrom Jan 9, 2026
Merged
Use pretty-assertions and improve debug implementation of Key#19lhemala merged 2 commits intolhemala:mainfrom
Key#19lhemala merged 2 commits intolhemala:mainfrom
Conversation
Owner
|
Thanks for the addition! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While writing tests and debugging #10, I had some trouble with the way keys and differences are displayed. To illustrate this, consider this code:
Without pretty-assertions and the key debug impl it will be displayed as

Without pretty-assertions, but the binary string debug impl

with just pretty-assertions:

and this is how it looks like with both pretty-assertions and the binary string debug impl: