|
You are here |
www.shuttle.dev | ||
| | | | |
articles.bchlr.de
|
|
| | | | | [AI summary] The article discusses challenges and workarounds for upcasting trait objects in Rust, exploring the limitations of dynamic dispatch and potential solutions through vtable structures and custom trait implementations. | |
| | | | |
aradaelli.com
|
|
| | | | | [AI summary] The author discusses their experience with the programming language D, highlighting its features, advantages over C/C++, and reasons for preferring it despite its niche status. | |
| | | | |
www.ncameron.org
|
|
| | | | | One of the more subtle aspects of Rust is how traits can be used as types. In this blog post I will attempt a bit of a deep dive into how to use traits as types and how to choose between the different forms. Preliminary: traits are not typesA type | |
| | | | |
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". | ||