Closed mxinden closed 3 years ago
@vmx @Stebalien does one of you have some time to give this pull request a review? I am sorry for the rather large change-set. Let me know in case you see a way to simplify the review work.
In a few weeks.
One thing that might be worth mentioning in the changelog/commit message is that you cannot any longer convert from an integer to a Protocol and back, though you have constants to get the integer values of protocols.
Addressed in https://github.com/multiformats/rust-multiaddr/pull/40/commits/11d6fcf5a359c38c101c46665f18b215b844528d.
It is not Copy any more, it might be worth mentioning in the changelog/commit message.
Addressed in https://github.com/multiformats/rust-multiaddr/pull/40/commits/11d6fcf5a359c38c101c46665f18b215b844528d.
@vmx thank you for the review. Would you mind taking another look?
In a few weeks.
@Stebalien I am interpreting this as an offer, not as a request to pause this pull request till then. Let me know if you would prefer to pause this pull request until you find time to review, after all this effort is in no rush.
Unless anything comes up, I will merge this sometime next week and cut the v0.12.0 release. Thanks @vmx for the help.
I am interpreting this as an offer, not as a request to pause this pull request till then.
Ah, no. It was an offer to ping me in a few weeks if this got stuck. Thanks @vmx!
parity-multiaddr
is a fork of this repository with various changes and additions. As part of https://github.com/libp2p/rust-libp2p/issues/758 this pull request does the following in order to merge the two while preserving the git history of both repositories:git subtree split
to extract https://github.com/libp2p/rust-libp2p/tree/master/misc/multiaddr to a separate git repository.Main merge happens via https://github.com/multiformats/rust-multiaddr/pull/40/commits/935a9664b4b12048fc0babbe734e69923b489a28. As far as I can tell all features of
multiaddr
andparity-multiaddr
are preserved. Naming closely followsparity-multiaddr
, thus crates depending onmultiaddr
(as far as I can tell none) will face breaking changes. In case of conflictsparity-multiaddr
is favored overmultiaddr
given that the former is more up-to-date and has a larger user base. Version is fast-forwarded tov0.12.0
to not conflict with existingparity-multiaddr
versions.