smol-rs
Add the into_stream() combinator
I assumed that was the status quo for futures_lite, like how zip and or are methods.
I guess it is only happening with methods that take two or more futures/streams. (e.g., catch_unwind is trait method only)
There has been discussion in the past in futures that freestanding functions are preferred for such methods: https://github.com/rust-lang/futures-rs/issues/1215
It seems you have removed the trait method, but I have the impression that into_ is a prefix that is often used in the method (e.g., String::into_bytes, {BufReader,BufWriter}::into_inner).
Maybe stream::from_future?
That said, I have no strong opinion on this as I tend to prefer the futures's APIs that take the future as an argument (i.e., I think stream::once is the ideal name here).
@smol-rs/admins: Any thoughts on the API here?
I agree with you about the naming. stream::once seems better to me as well.
I like the idea of stream::once, however, that method already exits and just yields a single value without being asynchronous. I renamed this type to stream::once_future().
So this does just the same as https://docs.rs/futures-util/0.3.24/futures_util/future/struct.IntoStream.html ? / https://docs.rs/futures-util/0.3.24/futures_util/stream/struct.Once.html
Yes, the idea is to give the user the ability to turn a Future into a Stream.