Forwarded from Альфина (телеграм-река)
здравствуйте. вас посетила КУКУШИЩА ПОВЫШЕННОЙ МОЩНОСТИ.
если вашу голову корёжит, перепостите её к себе, и она выкинет из гнезда всё, что представляет угрозу вашей собственной тщедушной кукушечке, и всячески её обиходит, обнимет могучими руками и обучит приёмам самообороны.
спасибо за внимание.
если вашу голову корёжит, перепостите её к себе, и она выкинет из гнезда всё, что представляет угрозу вашей собственной тщедушной кукушечке, и всячески её обиходит, обнимет могучими руками и обучит приёмам самообороны.
спасибо за внимание.
❤3😢3
Блог*
#prog #rust #rustasync #article How (and why) nextest uses tokio, part 1 Или хороший пример того, как async может пригодиться в программе, которая вообще никак не связана с общением по сети.
#prog #rust #rustasync #article
Why Async Rust
I often find async Rust to be misunderstood. Conversations around "why async" often focus on performance — a topic which is highly dependent on workloads, and results with people wholly talking past each other. While performance is not a bad reason to choose async Rust, we often we only notice performance when we experience a lack of it. So I want to instead on which features async Rust provides which aren't present in non-async Rust. Though we'll talk a bit about performance too at the end of this post.
---
But if the focus is more on the features async Rust enables, things like cancellation and timeouts quickly rise from nuisance to key reasons to adopt async Rust. Async Rust grants us the ability to control execution in a way which just isn't possible in non-async Rust. And frankly, isn't even possible in many other programming languages featuring async/.await either. The fact that an async fn compiles down to a lazy state machine instead of an eager managed task is a crucial distinction. And it means that we can author concurrency primitives entirely in library code, rather than needing to build it into the compiler or runtime.
Why Async Rust
I often find async Rust to be misunderstood. Conversations around "why async" often focus on performance — a topic which is highly dependent on workloads, and results with people wholly talking past each other. While performance is not a bad reason to choose async Rust, we often we only notice performance when we experience a lack of it. So I want to instead on which features async Rust provides which aren't present in non-async Rust. Though we'll talk a bit about performance too at the end of this post.
---
But if the focus is more on the features async Rust enables, things like cancellation and timeouts quickly rise from nuisance to key reasons to adopt async Rust. Async Rust grants us the ability to control execution in a way which just isn't possible in non-async Rust. And frankly, isn't even possible in many other programming languages featuring async/.await either. The fact that an async fn compiles down to a lazy state machine instead of an eager managed task is a crucial distinction. And it means that we can author concurrency primitives entirely in library code, rather than needing to build it into the compiler or runtime.
Yoshuawuyts
Why Async Rust
👍2🤔1
#prog #rust #rustasync #article
Futures and Segmented Stacks
Или немного о том, как модель исполнения растовых футур позволяет получить преимущества сегментированных стеков без их недостатков.
Futures and Segmented Stacks
Или немного о том, как модель исполнения растовых футур позволяет получить преимущества сегментированных стеков без их недостатков.
👍1🤔1🤡1
Как вы думаете, стоит ли на канале вводить хештег для материалов касательно async/await в Rust? Прецедент уже есть с rustlib и serde
👍38💩3
Forwarded from я что-то �� и всё ����
🔁 Developer Memes
"JetBrains"
submitted by Process2572
https://reddit.com/r/ProgrammerHumor/comments/xsz6t1/jetbrains/
"JetBrains"
submitted by Process2572
https://reddit.com/r/ProgrammerHumor/comments/xsz6t1/jetbrains/
👎6❤4😁4👍2