cargo-expand
flowistry
| cargo-expand | flowistry | |
|---|---|---|
| 16 | 15 | |
| 2,435 | 1,819 | |
| - | - | |
| 9.0 | 7.3 | |
| 14 days ago | 3 months ago | |
| Rust | Rust | |
| Apache License 2.0 | MIT License |
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.
flowistry
- An IDE plugin for Rust that helps you focus on relevant code
- Flowistry: an IDE plugin that analyzes the information flow of Rust programs, showing whether it's possible for one piece of code to affect another
-
Any data flow visualization tools?
https://github.com/willcrichton/flowistry https://github.com/cognitive-engineering-lab/aquascope
-
When do Rust's traits make your life difficult?
Hello Rustaceans, the same lab that has brought you The Rust Book Experiment, Aquascope, and Flowistry is starting a new endeavor. We want to understand when Rust's trait system makes it hard for you to understand or debug a Rust program.
-
rustc-plugin: A framework for writing plugins that integrate with the Rust compiler
I'm personally excited about building developer tools with a sophisticated understanding of your Rust programs. So I've worked on tools like Flowistry and Aquascope.
-
[blog] Rust should own its debugger experience
Maybe this vscode extension could be useful to you?
-
Plugins/extensions for the Rust Analyzer?..
Maybe you would be interested in flowistry?
- flowistry plugin?
-
Learn You an Agda (2014)
Quick, easy formal verification tools that programmers can use on the spot from the IDE are hard to make for most languages because most languages and their compilers weren't made with such thing in mind.
I guess Rust might be heading somewhere interesting with tooling, with tools like Flowistry existing (https://github.com/willcrichton/flowistry) showing what is possible. It's a plugin that can compute backwards / forwards static slices for you, straight in the IDE as a VSCode plugin. I think you need an external program that runs a full program analysis to do the same in C++.
-
Visual lifetime indicator
Based on how Flowistry works I think this should be possible.
What are some alternatives?
saito-rust - A high-performance (reference) implementation of Saito in Rust
rustviz - Interactively Visualizing Ownership and Borrowing for Rust
proc-macro-workshop - Learn to write Rust procedural macros [Rust Latam conference, Montevideo Uruguay, March 2019]
code2flow - Pretty good call graphs for dynamic languages
lol-html - Low output latency streaming HTML parser/rewriter with CSS selector-based API
Sourcetrail - Sourcetrail - free and open-source interactive source explorer
rust - Empowering everyone to build reliable and efficient software.
wslgit - Use Git installed in Bash on Windows/Windows Subsystem for Linux (WSL) from Windows and Visual Studio Code (VSCode)
quote - Rust quasi-quoting
dbgee - The zero-configuration debuggee for debuggers. Handy utility that allows you to launch CLI debuggers and VSCode debuggers from the debuggee side.
cargo-llvm-cov - Cargo subcommand to easily use LLVM source-based code coverage (-C instrument-coverage).
shisho - Lightweight static analyzer for several programming languages