Explore >> Select a destination
|
You are here 
|
adventures.michaelfbryan.com | ||
| | | | |
blog.m-ou.se
|
|
| | | | | Have you ever seen the Rust compiler give a Python error? Or better, have you ever seen rust-analyzer complain about Python syntax? In this post, we'll extend our python!{} macro to make that happen. | |
| | | | |
www.fastly.com
|
|
| | | | | Take a developer deep dive into Terrarium, our multi-language, browser-based editor and deployment platform at the edge. Learn how to compile Rust programs to WebAssembly right on your local machine, interact with the Terrarium system, and explore some applications weve built with it. | |
| | | | |
scorpiosoftware.net
|
|
| | | | | The Rust language ecosystem is growing each day, its popularity increasing, and with good reason. It's the only mainstream language that provides memory and concurrency safety at compile time, with a powerful and rich build system (cargo), and a growing number of packages (crates). My daily driver is still C++, as most of my work... | |
| | | | |
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. | ||
