Also I'm confused what the term "streaming stream" refers to. I need to name some things, and not sure how to correctly name them. I'd prefer not to (accidentally) use deviating terms, if possible.
-
-
Show this thread
-
cc/
@withoutboats@stjepang@steveklabnik if you have any insights here, they'd be very helpful!Show this thread
End of conversation
New conversation -
-
-
I find it depends per thing you apply it too. For example, in networking services I would refer to that as the connection or transport. If it were a file, I’d prob refer to it as the file.
-
hah, yeah -- my problem here is that I'm writing some generic code, so I have to refer to it as "the type that implements asyncread + asyncwrite", which as you said could be anything.
- 2 more replies
New conversation -
-
-
Can bytes be not raw in this case? I only label things as "raw" if there is a possibility of something else.
-
There are two kind of byte streams in async Rust: 1. AsyncRead / AsyncWrite -- which can only ever operate on bytes. 2. Stream<StreamItem = Vec<u8>> / Sink<SinkItem = Vec<u8>> -- which are generic over their types, but can choose to operate on bytes. Similar but different.
- 1 more reply
New conversation -
-
-
I tend to say "an async io"
-
or really just "an io"
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.