Introduce a separate Hash struct. #28
Merged
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.
This is intended to make the API clearer in separating the hash, which is part of the
GitOidbut not sufficient for representing theGitOid, from the overallGitOidstructure. TheGitOidcan be represented as a URI, or you can extract the parts (hash algorithm, object type, hash) individually. If you have theHash, now represented as a struct, you can either access the individual bytes through theDerefimpl oras_bytesmethod, or you can get the hexadecimal encoding through theDisplayimpl or the impliedto_stringmethod or explicithexmethod.Signed-off-by: Andrew Lilley Brinker alilleybrinker@gmail.com