https://blog.rust-lang.org/inside-rust/2022/02/03/async-in-2022.html
Obviously Rust needed more powerful abstractions, GAT (generic associated types) implementation stabilized, also going even further to HKT (higher kinded types, also referred as types of types, or type constructors), and dependent types, with following implementation of CoC (calculus of constructions).
And as a systems language there're a lot more things should be done to use Rust even more widely, espesially for embedded systems (automotive and aerospace sphere for example). For example, fault tolerance to run-time memory allocation exceptions in stdlib collections, dealing with infallible methods (panic on allocation failure in operations with collections), more improved error handling (to handle panics in main thread), and process recovering, after alloc errors, not yet fully supported in Rust stdlib's collections API (see this issue: https://github.com/rust-lang/rust/issues/29802).
Obviously Rust needed more powerful abstractions, GAT (generic associated types) implementation stabilized, also going even further to HKT (higher kinded types, also referred as types of types, or type constructors), and dependent types, with following implementation of CoC (calculus of constructions).
And as a systems language there're a lot more things should be done to use Rust even more widely, espesially for embedded systems (automotive and aerospace sphere for example). For example, fault tolerance to run-time memory allocation exceptions in stdlib collections, dealing with infallible methods (panic on allocation failure in operations with collections), more improved error handling (to handle panics in main thread), and process recovering, after alloc errors, not yet fully supported in Rust stdlib's collections API (see this issue: https://github.com/rust-lang/rust/issues/29802).