Skip to content

Conversation

@dignifiedquire
Copy link
Contributor

It turned out currently the coding mod is already public, simply hidden from the docs.

It seems to be the minimal change to allow using this functionality for VarInt is to document it and not hide it.

Fixes #1277

Copy link
Member

@djc djc left a comment

Choose a reason for hiding this comment

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

Seems reasonable to me. @Ralith thoughts?

Copy link
Collaborator

@Ralith Ralith left a comment

Choose a reason for hiding this comment

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

The idea of exposing this seems reasonable. Some cosmetic feedback to help with clarity.

@Ralith
Copy link
Collaborator

Ralith commented Dec 12, 2024

Worth noting that this is not the most minimal possible way to export VarInt encoding/decoding, since it also exposes logic for a handful of other simple std types, but I think it is a fairly natural place to redraw the encapsulation boundary for the benefit of protocols that reuse simple encoding patterns from QUIC, which are not necessarily limited to VarInt.

@djc
Copy link
Member

djc commented Dec 12, 2024

Can you squash these commits?

It turned out currently the `coding` mod is already public, simply hidden from the docs.

It seems to be the minimal change to allow using this functionality for `VarInt` is to document it and not hide it.

Fixes quinn-rs#1277
@djc djc added this pull request to the merge queue Dec 12, 2024
Merged via the queue into quinn-rs:main with commit 7647bd0 Dec 12, 2024
18 checks passed
@dignifiedquire dignifiedquire deleted the feat-varint-coding branch December 12, 2024 21:18
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.

Expose encoding and decoding of VarInt

3 participants