Blog post: Future::join and const-eval

1. tokio

   1 219 28,182 9.5 Rust

   A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...

   

   This is not about the task panicing or aborting. It's about the parent task (scope owner) panicing or abort - e.g. because it's inside a select!. In that case the child tasks are now unowned, and it's tricky to find a good solution on what you do with them. The same would totally apply to async-std or any other current async rust runtime. The unfortunately rather long discussion in 1879 describes it. The whole design and implementation for this had been fairly agnostic to any runtime. All it needs is a spawn function and join handles. Those were hardcoded to tokios, but that doesn't mean it couldn't be either generalized or ported somewhere else. But the same set of challenges will apply.

2. CodeRabbit

   coderabbit.ai featured

   CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

   

3. rfcs

   2 680 6,088 9.5 Markdown

   RFCs for changes to Rust

   

   There have been a few Pre-RFCs and at least one actual RFC about varidic generics by the way, just none that looked very realistic (IMHO). Here's the first one I found in my browser history: RFC2775.

4. tuple_fut

   3 1 0 0.0 Rust

   join and select as methods on tuples instead of macros

   

   I was bored tonight and just read this thread. So I tried to see if I could implement .join() and .select() on tuples. Well yes, you can, and it's not that complicated. https://github.com/miquels/tuple_fut

Suggest a related project