[sudeepj]

I am guessing you are a point D/D' in the diagram [1] Although the diagram is for the Rust overall, I think something similar is true for async Rust.

All I would say is hang in there. It gets better (from my experience).

Rust is not something you can code along as you think. There is a bit a of upfront thinking what the data-structures & data-flow look like.

At present, I can know in advance without writing code whether implementation I am thinking in Rust will work or not (work => satisfy Rust compiler)

[1] https://imgur.com/kNkV7jm

[orthoxerox]

> Rust is not something you can code along as you think.

This is my biggest gripe with Rust. I want to write code that produces the right result first and make it safe later.

[majewsky]

We already have too much code that "can be made safe later", but never is.

[carols10cents]

If you're interested in continuing with Rust, I'd suggest that you think about making code that produces the right result first and make it fast later: use `clone` everywhere you run into borrowing problems, use `Rc` or `Arc` instead of references everywhere you run into ownership problems, make the single threaded version work before adding concurrency, etc.