Skip to content
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

WIP: Depend on hex 1.0.0-alpha.0 #163

Closed
wants to merge 1 commit into from

Conversation

tcharding
Copy link
Member

We are attempting to do some release trickery in order to stabalize hex more quickly. It was observed that we only need the hex error types in the public API of downstream bitcoin crates that we want to stabalize. So we created a 1.0 that was just the parsing logci and error types.

Depend on the new hex 1.0.0-alpha.0 crate and re-export all its types and traits in the same spot as they were here.

@tcharding
Copy link
Member Author

This tests #162. Expect CI to fail because we patch the manifest.

We are attempting to do some release trickery in order to stabalize hex
more quickly. It was observed that we only need the `hex` error types in
the public API of downstream bitcoin crates that we want to stabalize.
So we created a 1.0 that was just the parsing logci and error types.

Depend on the new `hex 1.0.0-alpha.0` crate and re-export all its types
and traits in the same spot as they were here.
@tcharding
Copy link
Member Author

tcharding commented Feb 27, 2025

Ugh, we still can't do this with the make-everything-private version in #162 because we cannot remove HexToBytesIter (since its private in 1.0) and we cannot keep it because it requires error constructors.

How much developer time are we willing to spend chasing this unicorn of the perfect 1.0 crate?

EDIT: We could delete the now-private things in 1.0 from 0.4, and if users where using them they have to depend on 0.3 as well - <insert explicitive here>?

@tcharding
Copy link
Member Author

I believe this is a lost cause.

@tcharding tcharding closed this Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant