iroha VS embassy

I can show you a real world example: https://github.com/hyperledger/iroha The C++ version compiles in 3 minutes. The rust version takes 15, and the Rust version isn't even complete yet. Moreover, the target dir grows to sometimes in excess of 50GiB, if you have debug symbols, several features and incremental compilation. C++ by contrast keeps it in the low 8GiB which allows me to mount it to tmpfs.

There are no Rust files or Cargo.toml files in this repo: https://github.com/Hyperledger/Iroha

My daily work is developing an open source Rust blockchain. Our team is small, so we appreciate any help. You can take a look here: https://github.com/hyperledger/iroha/tree/iroha2-dev

> Blockchains are designed to be a network of peers, but not designed such that it’s really possible for your mobile device...

If I am not mistaken Hyperledger Iroha[0] has(had?) that as one of its goals.

[0] https://github.com/hyperledger/iroha

thanks. looked that up. for the curious: https://embassy.dev/

Running the Embassy RP2040 USB CDC ACM serial example takes about 5 seconds on a Pico.

https://github.com/embassy-rs/embassy/blob/main/examples/rp/...

Async solves different problems, you can, for instance, have just a single-threaded CPU and still have a nice API if you have async-await. It might not be so cool at a higher level as Go's approach of channels and threads, but it's cool in embedded, read this:

https://github.com/embassy-rs/embassy?tab=readme-ov-file#rus...

"Rust's async/await allows for unprecedently easy and efficient multitasking in embedded systems. Tasks get transformed at compile time into state machines that get run cooperatively. It requires no dynamic memory allocation, and runs on a single stack, so no per-task stack size tuning is required. It obsoletes the need for a traditional RTOS with kernel context switching, and is faster and smaller than one!"

I'm just toying with Raspberry Pi Pico and it's pretty nice.

Go and Rust have different use cases, the async-await is nice at a low level.

I have not yet dipped by toes in the Rust waters, but reading about the embassy project is actually what piqued my curiosity about using C++ coroutines in embedded. Are you familiar with the project or have you found it lacking?

I think I get the basics (shoutout to the Rust Embedded Working Group!), and I've started looking for the stack I'd be using. I think Embassy is really amazing, as well as the work of the ESP team -- hats off.

> }

And this is how to do it using embassy, which is an async framework for embedded in rust:

https://github.com/embassy-rs/embassy/blob/main/examples/rp/...

> not good for embedded

embassy begs to differ

https://embassy.dev/

async/await is really just a syntax for building state machines in a way that resembles regular code. It's compiled down to the same code that you would write by hand anyway (early on it had some bloat in state size but I think it's all fixed now).

And embedded has a lot of state machines!

You can run multiple executors at different interrupt priority levels (with multiple tasks per executor), which allows tasks on the higher priority executor to interrupt other tasks. Here's an example https://github.com/embassy-rs/embassy/blob/main/examples/nrf...