Тёмный

RustConf 2022 - ASYNC RUST: PAST, PRESENT, AND FUTURE GENERAL by Nick Cameron 

Rust
Подписаться 63 тыс.
Просмотров 21 тыс.
50% 1

Today, async and await are stable parts of the language, but you can't actually run async code without a third party runtime. Unlike most languages, an async function has to be awaited before any work gets done. Cancellation can happen at any time and can cause surprising errors. Why is async Rust this way? And how is it changing? This talk will cover the design decisions and trade-offs which led to the current design, what that design means for async programming today, and what the Async Working Group is doing to make it better: our plans, current status, and ongoing work.

Опубликовано:

 

13 сен 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 8   
@stIncMale
@stIncMale 2 года назад
9:29 "concurrent, but not parallel execution of these futures" - thank you for choosing words precisely! :)
@sodiumsalt
@sodiumsalt 2 года назад
It is somewhat parallel too in the sense that multiple futures may be polled simultaneously by the runtime.
@capability-snob
@capability-snob 2 года назад
Interesting challenges! I'm glad that Rust went the intuitive way. Futures force you to think about progress and concurrency in the same way types force you to think about what data is valid for an operation, so they are primarily a safety thing afaiac.
@Xgroleau
@Xgroleau 2 года назад
Looking forward for the Rust async development! I'm glad rust is keeping everything available for whatever the runtime is. Async on embedded is very natural since most operations are I/O. I recently encountered that async recursive functions are only available via boxing, which makes sense since you need to store the state recursively. Would it be theoretically possible via tail loop optimizations to have recursive functions without boxing?
@AbelShields
@AbelShields 2 года назад
Interesting talk, it does a good job at highlighting some of the intricacies around async code in Rust and the reason why these new features can take a while. Is there any news on generics over sync/async? I've heard it's causing duplicated blocking/non-blocking versions of code in libraries and I haven't seen much discussion except for an article on algebraic effects (plus a really cool, if a little weird-looking library implementing them in Rust)
@a314
@a314 Год назад
What's the state of structured concurrency with Rust?
@ZekeFast
@ZekeFast 9 месяцев назад
12:00 This soon took awhile to get RPITIT in stable, but with 1.74.0 Rust finally got there! And GATs Rust stabilized at 1.65.0.
@muezsier
@muezsier 2 года назад
Nice presentation 👍
Далее
Как подписать? 😂 #shorts
00:10
Просмотров 1,4 млн
P99 CONF - Zig vs Rust
55:01
Просмотров 73 тыс.
RustConf 2023 - How Powerful is Const
22:58
Просмотров 14 тыс.
Async Rust Is A Bad Language | Prime Reacts
28:46
Просмотров 95 тыс.