Explore >> Select a destination
|
You are here 
|
radu-matei.com | ||
| | | | |
blog.pnkfx.org
|
|
| | | | | ? This post is the first part in a planned series on linking Rust crates. My desire is to get informal feedback on these posts, and then turn ... | |
| | | | |
robert.kra.hn
|
|
| | | | | Wrapping heavy dependencies as dynamic libraries can help during development. | |
| | | | |
damienradtke.com
|
|
| | | | | ||
| | | | |
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. | ||
