Move Arbitrary instances from cardano-ledger to cardano-binary#618
Draft
neilmayhew wants to merge 2 commits intomasterfrom
Draft
Move Arbitrary instances from cardano-ledger to cardano-binary#618neilmayhew wants to merge 2 commits intomasterfrom
Arbitrary instances from cardano-ledger to cardano-binary#618neilmayhew wants to merge 2 commits intomasterfrom
Conversation
lehins
reviewed
Feb 4, 2026
Collaborator
lehins
left a comment
There was a problem hiding this comment.
Let's not move these instances at this point and wait till we have a necessary breaking change to cardano-binary
2a3ce44 to
27c5b7e
Compare
27c5b7e to
a74db21
Compare
a74db21 to
2f6ef54
Compare
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.
Description
The instances are for:
ByteArray,SlicedByteArrayandTermfromcborgChecklist
CHANGELOG.mdfor the affected packages.New section is never added with the code changes. (See RELEASING.md)
.cabalandCHANGELOG.mdfiles according to theversioning process.
.cabalfiles for all affected packages are updated.If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)