https://jason5lee.me/tags/async/ Recent content in Async on Jason5Lee's Blog Hugo en-us Sat, 24 Jun 2023 19:35:34 +0000 https://jason5lee.me/blog/understanding-coroutines/ Sat, 24 Jun 2023 19:35:34 +0000 https://jason5lee.me/blog/understanding-coroutines/ <p>We often need to execute multiple tasks simultaneously in the program, such as a server handling multiple requests at the same time or a browser rendering the UI while performing I/O operations. As concurrency in our programs increases, technologies like asynchronous I/O, coroutines, and async/await are being used to support it. In this article, I&rsquo;ll share my understanding of these technologies, hoping to help you comprehend and apply them.</p> <h2 id="the-fundamental-idea-of-coroutines">The Fundamental Idea of Coroutines</h2> <p>The OS provides threads to run parallel tasks, but creating and scheduling a lot of threads can lead to high costs. Even with thread pooling, if a large amount of concurrency is needed at the same time, the number of threads in the thread pool must also be large.</p> https://jason5lee.me/blog/rust-exception-async/ Fri, 11 Mar 2022 22:40:23 +0000 https://jason5lee.me/blog/rust-exception-async/ <p><strong>WARNING</strong>: This may be a bad practice. The point of this article is just to share my idea.</p> <p>Exception is a popular feature in many programming languages. Unlike Rust where errors are considered as a return value of the <code>Err</code> case of <code>Result</code>, in these languages errors are thrown like <code>panic</code>. The caller may catch the errors and process them similar to <code>catch_unwind</code> in Rust. Different people may have different preferences on the error handling style, but panic-unwind is always considered a bad practice and should be avoided if possible. So using exception-like error handling in Rust is impossible.</p>