|
You are here |
without.boats | ||
| | | | |
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. | |
| | | | |
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 ... | |
| | | | |
boats.gitlab.io
|
|
| | | | | It's hard to believe its been almost 6 weeks since the last post I made about async/await in Rust. So much has happened that these last several weeks have flown by. We've made exceptionally good progress on solving the problem laid out in the first post of this series, and I want to document it all for everyone. Future and the pinning API Last month I wrote an RFC called "Standard library API for immovable types". | |
| | | | |
www.shuttle.dev
|
|
| | | Building and deploying a notification service in Rust with Axum and AWS SNS | ||