Explore >> Select a destination
|
You are here 
|
blog.gnoack.org | ||
| | | | |
www.hhyu.org
|
|
| | | | | Science, programming, books, and other interesting stuff | |
| | | | |
lewissbaker.github.io
|
|
| | | | | A tweak was made to the design of coroutines in 2018 to add a capability called "symmetric transfer" which allows you to suspend one coroutine and resume another coroutine without consuming any additional stack-space. The addition of this capability lifted a key limitation of the Coroutines TS and allows for much simpler and more efficient implementation of async coroutine types without sacrificing any of the safety aspects needed to guard against stack-overflow. In this post will attempt to explain the stack-overflow problem and how the addition of this key "symmetric transfer" capability lets us solve this problem. | |
| | | | |
andreabergia.com
|
|
| | | | | Error handling is a fundamental aspect of programming. Unless you are writing hello world, you will need to handle errors in your code. In this post, I will discuss a bit the most common approaches used by various programming languages. Return error codes This is one of the most ancient strategies - if a function can fail, it can simply return an error code - often a negative number, or null. | |
| | | | |
0x00.cl
|
|
| | | Tomas Gutierrez L. personal website (0x00) | ||
