tokio::spawn should have task names

[Milo123459]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Using the console, it would be nice if hyper had some task names
Describe the solution you'd like
A clear and concise description of what you want to happen.
Implement a custom function for spawning something with a named parameter. Here is some code I wrote up:

pub fn spawn_named<T>(
	name: &str,
	future: impl std::future::Future<Output = T> + Send + 'static,
) -> tokio::task::JoinHandle<T>
where
	T: Send + 'static,
{
	#[cfg(tokio_unstable)]
	return tokio::task::Builder::new().name(name).spawn(future);

	#[cfg(not(tokio_unstable))]
	tokio::spawn(future)
}

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
N/A
Additional context
Add any other context or screenshots about the feature request here.

[seanmonstar]

Yea, I get what you mean. Though, as long as it's unstable in Tokio, I don't think we'd add support yet. That said, it's easily possible to provide a hyper::rt::Executor that uses that instead of depending on hyper's default.

[Milo123459]

Yea, I get what you mean. Though, as long as it's unstable in Tokio, I don't think we'd add support yet. That said, it's easily possible to provide a hyper::rt::Executor that uses that instead of depending on hyper's default.

I think we should prepare for the future, if you know what I mean. A few other libraries I use (serenity) have already implemented this and I think because serenity uses hyper, it'd be nice to see hyper implementing this as well.

[seanmonstar]

Unsure, but you can check in on the stabilization issue here: tokio-rs/tokio#4114