Skip to content
This repository was archived by the owner on Nov 30, 2022. It is now read-only.

Conversation

@stevenroose
Copy link
Collaborator

No description provided.

Copy link
Member

@apoelstra apoelstra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

@stevenroose stevenroose force-pushed the tagged-newtype branch 4 times, most recently from 8f5b002 to c46d75f Compare October 7, 2020 21:35
Copy link
Member

@apoelstra apoelstra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

re-utACK

@dr-orlovsky
Copy link
Contributor

confirm my ACK

@apoelstra apoelstra merged commit 6b9c472 into rust-bitcoin:master Oct 7, 2020
@dr-orlovsky
Copy link
Contributor

Just understood that this macro uses hash_newtype!, which implements Display and FromStr defaulting to reading/creating hexadecimal representation. However for certain tagged hashes types I use Bech32 encoding, and it's impossible to change that with this macro...

@stevenroose
Copy link
Collaborator Author

Why do you use bech32? Hmm yeah well the reason I had these in rust-bitcoin in a taproot module was partly to make sure this wouldn't grow larger than just taproot usage. But still I think as long as there is no Bitcoin usage of tagged hashes that serializes differently, I think it's fine here.

It's really not super hard to specify an alternative macro in your project to create bech32 tagged hash newtypes, right?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants