Skip to content

Conversation

@thomaseizinger
Copy link
Contributor

@thomaseizinger thomaseizinger commented Nov 2, 2023

Description

Resolves: #4489.
Resolves: #2500.

Notes & open questions

Change checklist

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • A changelog entry has been made in the appropriate crates

@thomaseizinger thomaseizinger added send-it trivial Marks PRs which are considered trivial and don't need approval from another maintainer. labels Nov 2, 2023
@mergify mergify bot merged commit d05d836 into master Nov 2, 2023
@mergify mergify bot deleted the refactor/autonat-framed branch November 2, 2023 07:26
mergify bot pushed a commit that referenced this pull request Nov 2, 2023
As described in #4011, these utility functions don't belong in `libp2p-core`. Users can use `quick-protobuf-codec` if they need to write varint-prefixed protobuf messages. For writing varint-prefixed bytes, the `unsigned-varint` crate offers a various codec implementations.

`libp2p-core` is the base dependency of all other crates. Thus, we should only expose items there that are actually needed by all other crates. For implementation details like how bytes are written, downstream crates (including users) should reach for other crates.

Depends-On: #4787.
Resolves: #4011.

Pull-Request: #4788.
umgefahren pushed a commit to umgefahren/rust-libp2p that referenced this pull request Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

send-it trivial Marks PRs which are considered trivial and don't need approval from another maintainer.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

autonat: migrate to quick-protobuf-codec Migrate all protocols to use quick-protobuf-codec

2 participants