I really dislike that derive macros have to essentially ship their own parser to access some form of AST: introspection would solve that and yeah, we missed out on that rustconf talk + work, didn't we.
@fasterthanlime Not just ship their own parser, but also a greedy parser at that. Want to look at a function signature? Better parse its body down to the last tiny statement!
Venial (https://github.com/PoignardAzur/venial) at least got that particular part right, but it's a hard sell basically because nobody's using it and is still lacking features.
The whole thing is just a bit sad IMO. There's not even that many people who understand proc macros or learning materials to teach them.
re offline Rust: everything in crate docs, or rustdoc (the cargo manual, incl. unstable features, etc.) you can take with, but, for example, neither serde_derive nor serde_macros actual documents container/field attributes.
I had the same issue with at least another crate, the rust doc comments were pretty short and linked to the website heavily, which... I wish I thought about httrack'ing before the flight, but, reader, I didn't.
I'm trying to get better at delivering "bad news" earlier.
If I'm not gonna make it to an event, or won't have time to finish a task, I don't wait until the last minute to communicate that — I let them know as soon as I know.