cargo-expand
proc-macro-workshop
cargo-expand | proc-macro-workshop | |
---|---|---|
16 | 26 | |
2,435 | 3,816 | |
- | - | |
9.0 | 4.3 | |
14 days ago | 23 days ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cargo-expand
-
What is Rust doing behind the scenes?
It's been superseded by https://github.com/dtolnay/cargo-expand
-
Why dereferencing coercion is not used here?
Try installing cargo expand, it's useful to see how macros eventually get expanded. For example, if you run cargo expand on the following code
-
Procedural Macros are really hard to understand
You can use cargo expand to see what your code expands to: https://github.com/dtolnay/cargo-expand
-
[blog] Rust should own its debugger experience
Not too familiar with macros but does cargo-expand do what you want or did you mean something else?
-
Help me understand the borrowing and moving variable concept!
Yes. You can use Tools > Expand Macro on the playground or install and run cargo-expand to see what the macro expands to. It just adds a & before the argument.
- Advanced Metaprogramming in C: A select statement
-
How does declaring variables in macros work
cargo expand
-
How to see macro's source code in crate?
Along with what others are saying, there is also cargo expand which can show you what code a macro generates
-
How does Rust Python ffi work?
Something that may help you understand code with magic proc macros is this utility. It's basically a wrapper around a Rust compiler flag that allows you to expand macros for a file.
-
How does libtest know which functions are marked with #[test]?
You can use https://github.com/dtolnay/cargo-expand to examine how it works.
proc-macro-workshop
-
Why does the core not provide a "New" derive attribute?
Tangentially, the proc macro workshop walks through building a derive macro implementing a builder pattern. From experience, I can tell I couldn't ever write proc macros just by reading the manual, going through it is really helpful https://github.com/dtolnay/proc-macro-workshop/blob/master/README.md
-
Help on spans for proc macros
I am working on the proc macro workshop and am a little stuck on the builder portion of the workshop. Step 08-unrecognized-attributes wants you to handle the car where the field modifier has a misspelled portion (eac instead of each)
-
Practical Procedural Macros in Rust
I would very much second the suggestion to do David Tolnay’s Proc Macro Workshop if you want to start understanding how to write them. I’d been writing Rust for years but always kind of avoided proc macros.
When I had a need for them, I went through only the first section of the workshop and everything clicked. You can just do the derive macro section and all the strange and scary-looking macro syntax will make sense. I realized that there is only a bit of extra syntax but it’s used very often so it can seem a little overwhelming when reading macro code.
https://github.com/dtolnay/proc-macro-workshop
- Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022
-
A walkthough on how to write derive procedural macros
Another good one imo is the proc-macro-workshop.
-
Transitioning to Rust as a company
Don't be afraid of proc macros and derive macros, they rule. Study the basic examples. Crates like darling and resources like David Tolnay's workshop will help. Write derives for your simpler traits and impress your colleagues.
-
What are your experiences with hack-and-learn events?
Regarding 4, I think that macros are an interesting intermediate/advanced topic. I personally loved the material from https://github.com/dtolnay/proc-macro-workshop
-
Procedural Macros are really hard to understand
It took me a while to get anything done. My mistake : I came accross the procedural macros workshop several times, and every time I dismissed it, thinking - meh I'll just hack together exactly what I need and move on. Then finally I figured there is no way around it. The builder exercise sounds boring but it covers the topic pretty well. And then I went on to the debug one and from there was able to build the proc macro I wanted.
-
MacroKata is really good!
Hey! While researching, I found this: https://github.com/dtolnay/proc-macro-workshop
-
Anything C can do Rust can do Better
Rust Latam: procedural macros workshop - David Tolnay
What are some alternatives?
saito-rust - A high-performance (reference) implementation of Saito in Rust
sccache - Sccache is a ccache-like tool. It is used as a compiler wrapper and avoids compilation when possible. Sccache has the capability to utilize caching in remote storage environments, including various cloud storage options, or alternatively, in local storage.
lol-html - Low output latency streaming HTML parser/rewriter with CSS selector-based API
rust-learnings - Collection of Rust learnings through implementation
rust - Empowering everyone to build reliable and efficient software.
style - css for rust
quote - Rust quasi-quoting
cargo-llvm-cov - Cargo subcommand to easily use LLVM source-based code coverage (-C instrument-coverage).
style - Style Dart Backend Framework
rustviz - Interactively Visualizing Ownership and Borrowing for Rust
num-bigint - Big integer types for Rust