-
Notifications
You must be signed in to change notification settings - Fork 200
types: make Malleability an enum #1037
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
guggero
wants to merge
5
commits into
rust-bitcoin:master
Choose a base branch
from
guggero:malleable-enum
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
9e27785
test(typeck): only check the malleability properties where they hold
guggero a37a160
types: make Malleability an enum
guggero 4817382
refactor: rename and deprecate requires_sig
guggero dc60507
test(typeck): pin the erasure of the malleability properties
guggero fab8f9b
test(satisfy): document timelock malleability regression 1037
guggero File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In 4817382:
This deprecation is in the wrong place and its message makes no sense. We should deprecate the
requires_sigmethod, telling users to usenon_malleable_and_requires_siginstead. And we should not deprecate the new method.Did Claude do this (introducing a new method and immediately deprecating it)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, I might have misunderstood your earlier comment.
The
requires_sigmethod did exist before this PR. And your comment stated: "In addition to updating the docs we should also deprecate this and rename it tonon_malleable_and_requires_sig.".Which is what I did (with Claude, yes).
But it sounds like you might have meant something like "introduce a new, fixed method called
non_malleable_and_requires_sig"?And yes, the deprecation comment definitely isn't my best work, happy to use a better wording if you have a suggestion.