Explore >> Select a destination
|
You are here 
|
tokio.rs | ||
| | | | |
erikmcclure.com
|
|
| | | | | One of the most fundamental problems with Rust is the design of Result. It is a lightweight, standardized error return value, similar to C-style error codes but implemented at a type system level that can contain arbitrary information. They are easy to use and very useful, and the ecosystem encourages you to use them over panic! whenever possible. Unfortunately, this ends up creating a problem. Result is not like a C++ exception because it doesn't contain a stacktrace by default, nor does the compiler have any idea where it was first constructed, unless the error type it contains decides to include that information upon construction by using backtrace. | |
| | | | |
blog.sylver.dev
|
|
| | | | | In this episode, we'll extend our server to serve static files. We'll also refactor our code to support connection reuse, and implement a graceful shutdown mechanism. If your didn't follow the previous episode, you can find the code on GitHub. As we ... | |
| | | | |
async.rs
|
|
| | | | | ||
| | | | |
avestura.dev
|
|
| | | What are the problems of C, and how Zig addresses them? | ||
