/explore
|
You are here 
|
deniskyashif.com | ||
| | | | |
without.boats
|
|
| | | | | [AI summary] The text discusses the differences between the buffered stream pattern and the scoped task pattern in Rust, focusing on how they can lead to deadlocks. It highlights that both patterns can result in deadlocks due to bounded resources like channels or limited concurrent futures, but the scoped task pattern is generally safer because it makes dependencies explicit through synchronization primitives. The text also emphasizes the importance of the Rust borrow checker in preventing certain types of deadlocks by enforcing ownership and borrowing rules. | |
| | | | |
www.wingolog.org
|
|
| | | | | wingolog: article: a new concurrent ml | |
| | | | |
ghcmutterings.wordpress.com
|
|
| | | | | If you want to make programs go faster on parallel hardware, then you need some kind of concurrency. Right? In this article I'd like to explain why the above statement is false, and why we should be very clear about the distinction between concurrency and parallelism. I should stress that these ideas are not mine,... | |
| | | | |
blog.yoshuawuyts.com
|
|
| | | [AI summary] A deep dive into async Rust's cancellation mechanics, covering futures, tasks, propagation issues, structured concurrency, and future language directions. | ||
