Explore >> Select a destination
|
You are here 
|
evilcookie.de | ||
| | | | |
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 ... | |
| | | | |
blog.sylver.dev
|
|
| | | | | Build a web server with Rust and tokio - Part 0: the simplest possible GET handler Welcome to this series of blog posts where we will be exploring how to build a web server from scratch using the Rust programming language. We will be taking a hands-o... | |
| | | | |
mbuffett.com
|
|
| | | | | Recently I've been working on a project to surface census data via a GraphQL API, mostly as a way to learn GraphQL. I did end up learning GraphQL, but I also ended up learning a lot about proc macros. I was using Juniper, which creates a GraphQL schema using structs like this: #[derive(GraphQLObject, Copy, Clone, Debug)] struct Demographics { female: Option, male: Option, } The problem, is that the census data I was looking to surface had way too many variables, I would have had to write out 207 structs, with a total of 352 fields. Here's a nice tree-view of the census data, courtesy of the frangipanni tool. Obviously, I didn't want to write out all these structs and fields by hand, even with some fancy vim macros that would have been too much tedious work for a side project that's supposed to be fun. | |
| | | | |
nikgrozev.com
|
|
| | | Most software engineers know about operating system (OS) level processes and threads. They are taught in all university OS courses. However, newer concepts p... | ||
