Fast-path zero-byte reads in WebSocketsTelemetryStream ReadAsync #1435
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.
Followup to #1415
A
Consume
of zero bytes is a no-op on the parser, so we can just return the original read task to the caller.Since we are always doing zero-byte reads, this effectively means that if the underlying stream supports it,
WebSocketsTelemetryStream
'sReadAsync
will never allocate.