Explore >> Select a destination
|
You are here 
|
ohadravid.github.io | ||
| | | | |
without.boats
|
|
| | | | | ||
| | | | |
tokio.rs
|
|
| | | | | Tokio is a runtime for writing reliable asynchronous applications with Rust. It provides async I/O, networking, scheduling, timers, and more. | |
| | | | |
boats.gitlab.io
|
|
| | | | | It's hard to believe its been almost 6 weeks since the last post I made about async/await in Rust. So much has happened that these last several weeks have flown by. We've made exceptionally good progress on solving the problem laid out in the first post of this series, and I want to document it all for everyone. Future and the pinning API Last month I wrote an RFC called "Standard library API for immovable types". | |
| | | | |
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. | ||
