Explore >> Select a destination
|
You are here 
|
blog.logrocket.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. | |
| | | | |
developerlife.com
|
|
| | | | | Procedural macros are a way for you to extend the Rust compiler and provide plugins that you can use to extend the language. They allow you to reduce the need to write manual boilerplate code, and even allow you to create your own DSL (domain specific language). This article goes into the details of creating the 3 kinds of procedural macros in Rust. | |
| | | | |
blog.jetbrains.com
|
|
| | | | | Have you ever wondered how Rust's procedural macros work? In this blog post series, we will get into the details! A member of our team, Vladislav Beskrovny, recently gave a talk on the topic at RustCo | |
| | | | |
akaptur.github.com
|
|
| | | Last Thursday I gave a lightning talk at Hacker School about the peephole optimizer in Python. A "peephole optimization" is a compiler ... | ||
