I think the LocalRuntime is useful. However, I'd like to hit the brakes for now, there are more works we need to do before stabilizing it in the code. Removing the tokio_unstable from the code should be the last work for stabilization.

1. Shall we deprecate the tokio::task::LocalSet and tokio_util::task::LocalPoolHandle?
2. There are many overlaps between the LocalRuntime and CurrentThreadRuntime, what's the future of the current thread runtime? Any guideline to downstream?
3. Shall we add the tokio::spawn_local? What's the behavior when it is called from current_thread or multi_thread runtime?
4. Any other impacts to the existing usage of tokio, tokio-stream, and tokio-util?

Relevant to this: #6741

LocalRuntime is very helpful for me, thanks!

I think it's better to add description of flavor = "local in the doc comment of tokio::test as well as tokio::main.
Like the following:
(Sorry, but I couldn't comment it on source code due to GitHub UI)

/// # local runtime
///
/// The default test runtime is the [local runtime]. The [local runtime] is similar to the current-thread
/// but supports[`task::spawn_local`](../tokio/task/fn.spawn_local.html).
///
/// ```no_run
/// #[tokio::test(flavor = "local")]
/// async fn my_test() {
///     assert!(true);
/// }
/// ```

Hi @Daksh14, are you willing to re-open this PR? Based on #6739 (comment), I think we can continue this work.