All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Async Rust's binary bloat problem: Seeking compiler-level solutions for embedded systems

By

Dion

26d ago· 12 min readenOpinion

Summary

The article discusses the problem of binary size bloat in async Rust, particularly affecting microcontrollers and embedded systems. The author explains that async Rust introduces significant overhead despite promises of zero-cost abstractions. They have previously outlined workarounds but prefer a compiler-level solution, having submitted a Project Goal and seeking funding to address the issue at its root.

Key quotes

· 3 pulled
I love me some async Rust! It's amazing how we can write executor agnostic code that can run concurrently on huge servers and tiny microcontrollers.
But especially on those tiny microcontrollers we notice that async Rust is far from the zero cost abstractions we were promised.
That's because every byte of binary size counts and async introduces a lot of bloat.
Snippet from the RSS feed
I've previously explained async bloat and some work-arounds for it, but would much prefer to solve the issue at the root, in the compiler. I've submitted a Project Goal, and am looking for help to ...

You might also wanna read