rust-tokio

This question already has an answer here: Why does the Rust compiler request I constrain a generic type parameter's lifetime (error E0309)? 1 answer Why is the bound `T: 'a` required in order to store a reference `&'a T`? 2 answers The compiler suggests I add a 'static lifetime because the parameter type may not live long enough, but I don't think that's what I want 2 answers I thought that I've got what the 'static lifetime is, but now I'm not sure. I'm trying to understand how to work with Tokio and Futures. My app is working, but the structure is awful, so I need to decompose it. Here comes

The async example is useful, but being new to Rust and Tokio, I am struggling to work out how to do N requests at once, using URLs from a vector, and creating an iterator of the response HTML for each URL as a string. How could this be done? As of reqwest 0.9: use futures::{stream, Future, Stream}; // 0.1.26 use reqwest::r#async::Client; // 0.9.14 use tokio; // 0.1.18 type Result<T> = std::result::Result<T, Box<std::error::Error>>; const PARALLEL_REQUESTS: usize = 2; fn main() -> Result<()> { let client = Client::new(); let urls = vec!["https://api.ipify.org", "https://api.ipify.org"]; let

I want to implement a futures::Stream for reading and parsing the standard output of a child subprocess. What I'm doing at the moment: spawn subprocess and obtain its stdout via std::process methods: let child = Command::new(...).stdout(Stdio.pipe()).spawn().expect(...) add AsyncRead and BufRead to stdout: let stdout = BufReader::new(tokio_io::io::AllowStdIo::new( child.stdout.expect("Failed to open stdout"), )); declare a wrapper struct for stdout: struct MyStream<Io: AsyncRead + BufRead> { io: Io, } implement Stream : impl<Io: AsyncRead + BufRead> Stream for MyStream<Io> { type Item =