We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The details of this probably depend on the Reader implementation, i.e., what does it mean that data is available.
Some examples:
read
If the user wants the whole buffer to be filled (unless we're at EOF), he can use the try_fill method which is being introduced in #18059.
try_fill
The text was updated successfully, but these errors were encountered:
It would see that this is implementation-specific, yeah. @aturon @alexcrichton is this kind of thing something to specify? /cc #21070
Sorry, something went wrong.
The current documentation of Read::read states:
Read::read
This function does not provide any guarantees about whether it blocks waiting for data
The Read trait has become much more general and I believe this issue is moot now.
Read
Auto merge of rust-lang#18106 - Veykril:push-yzsqoykyowts, r=Veykril
8cd0a27
fix: Don't report typed hole error in asm! out ops Fixes rust-lang/rust-analyzer#18103
No branches or pull requests
The details of this probably depend on the Reader implementation, i.e., what does it mean that data is available.
Some examples:
read
on the contained Reader if the buffer is not emptyIf the user wants the whole buffer to be filled (unless we're at EOF), he can use the
try_fill
method which is being introduced in #18059.The text was updated successfully, but these errors were encountered: