Query Transmit/Receive Buffer Counts #51
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
haydenridd
commented
Oct 9, 2025
| return error.Unexpected; | ||
| }, | ||
|
|
||
| .macos => {}, |
There was a problem hiding this comment.
I thought this was odd and should likely be a compile error instead of silent, but could be missing something!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've added in the ability to query the transmit/receive buffer counts for Linux and Windows (I don't have a Mac to test on)! This is particularly useful for the receive buffer, as a read call will block until there's a byte to be read. Added some basic tests that just make sure the counts are
0after a the buffers have been cleared.Verified this actually works as expected on Linux + Windows. One thing to note is I was never able to get the transmit buffer count to increment on Windows. However, it very well could be that the OS is simply flushing the buffer faster than I can query it immediately after writing.