|
You are here |
blog.japaric.io | ||
| | | | |
tmandry.gitlab.io
|
|
| | | | | My last post, The Rust Organization in 2021, was about how things got done. In this post, I want to talk about what I'd like to see get done: the biggest language, library, and compiler features I'd like to see in 2021. To be sure, this post is more of a "wish list," in the sense that it may not be possible to do all of it in a year. But these are the most important things I can think of to make progress on. | |
| | | | |
theincredibleholk.org
|
|
| | | | | As I've written about before, one of the major features we're working on adding to Rust is to allow async functions in traits. Today we have support in nightly ... | |
| | | | |
smallcultfollowing.com
|
|
| | | | | [AI summary] A developer explains the technical challenges of ensuring async trait functions return Send futures in Rust and proposes a syntax solution where function callers specify send requirements rather than enforcing them globally in the trait definition. | |
| | | | |
developerlife.com
|
|
| | | This article illustrates how to write concurrent and parallel code in Rust using Tokio. The pedagogical example we will use is building an asynchronous implementation of a middleware runner that you might find in a Redux store. | ||