✳flâneur — a map of the web's best reading

Async Rust: The new billion-dollar mistake?

kerkour.com · 258 words · saved by 1 readers

This post is part of my Summer Autumn of Rust 2024 series: weekly (or more) quickies about how to write great Rust code so you will be ready to rock at the end of the summer and find a new exciting job 🤘 Dont forget to Subscribe (Email & RSS) Tomy Hoare described his invention of null references (or null pointers) a "billion dollar mistake": I couldn't resist the temptation to put in a null reference, simply because it was so easy to implement. This has led to innumerable errors, vulnerabilities, and system crashes, which have probably caused a billion dollars of pain and damage in the last forty years. Today I will explain why I often call async/await the "new billion dollar mistake": a mistake that has probably caused billions in developer productivity and bugs in the past ten years, especially in the context of Rust. Function coloring is a well-known problem in programming circles since Bob Nystrom's 2015 article: What Color is Your Function?: "red (asynchronous) functions" can't c

` prop, to ensure that we render an actual element instead of a Render a single element as the child so that we can forward the props onto that element. Did you forget to passthrough the `ref` to the actual DOM node? Internal Error. Please try again and contact support if the problem persists. mx-auto max-w-xl transform divide-y divide-gray-100 overflow-hidden rounded-xl bg-[var(--mdninja-background)] shadow-2xl ring-1 ring-gray-200 transition-all Almost finished... We need to confirm your email address to prevent spam. To complete the subscription process, please click the link in the email w

Explore this link on the map →

related reading