Explore >> Select a destination
|
You are here 
|
rtpg.co | ||
| | | | |
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. | |
| | | | |
cprimozic.net
|
|
| | | | | ||
| | | | |
adventures.michaelfbryan.com
|
|
| | | | | Have you ever been in a situation where, because of how the code is structured, it's practically impossible to inject a dependency into the component that needs it? Even global variables - ubiquitously reviled for their ability to do "spooky action at a distance" - weren't spooky enough. In this article, I'll share a technique I discovered while working on a WebAssembly-based CAD package that allows for dependency injection at link time. This technique is particularly useful when traditional dependency injection methods aren't available or practical. | |
| | | | |
eranstiller.com
|
|
| | | Unlock your career potential in 2023! Discover the 75 top software engineering skills you need to stand out in the tech industry. Start learning today! | ||
