CodeLLDB
cargo-expand
CodeLLDB | cargo-expand | |
---|---|---|
23 | 16 | |
2,340 | 2,435 | |
- | - | |
6.1 | 9.0 | |
2 days ago | 12 days ago | |
Rust | Rust | |
MIT License | 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.
CodeLLDB
-
custom pretty printer/debug helpers for C++ debugging?
Ok, so apparently here they are called 'data formatters' instead of pretty printers or debug helpers... https://github.com/vadimcn/codelldb/wiki/Custom-Data-Formatters
-
Visualization tools when working with C++?
For debugging lldb supports python scripts: https://github.com/vadimcn/codelldb/wiki/Data-visualization
-
Zig Build System
I use VS Code on Linux to debug Zig. Haven't tried the others you mentioned, but it just emits standard DWARF symbols, so I'm guessing if you can debug C/C++ you could probably also do Zig with minimal changes? I just use the lldb VS code plugin[0], which works out of the box for me with no issues.
https://github.com/vadimcn/codelldb
-
How game-dev-s debug rust?
It's pretty bad, unfortunately. As you discovered, using the gnu toolchain works better with code-lldb (see more info here), but it still isn't great. CLion is a little better, but costs money and lacks support in other ways compared to VSCode.
- Debug rust program as root
-
Migrating from VSCode to Neovim
- I tried to install codelldb: https://github.com/vadimcn/vscode-lldb without success.
-
Does anyone here work in gamedev with Rust as their primary language?
Are you on Windows or Linux? On Windows I've had nothing but trouble getting code-lldb to display debug info for any sort of nontrivial data structure due to this issue, which means I need to switch to x86_64-pc-windows-gnu, but then that breaks other upstream crates that use cc to compile C++ code.
-
[blog] Rust should own its debugger experience
I've been using vscode-lldb with VS Code on macos, and I've been very happy with the experience so far.
-
i need some recommendations
Check this: https://github.com/vadimcn/vscode-lldb/wiki/Breakpoints-are-not-getting-hit
-
using VScode codeLLDB
yeah since they updated the rust compiler for windows to use a different style of debugger symbols and since they changed that in CodeLLDB the variables output have not been the same. Though i believe the owner has been trying to fix it. But any issues you do have report them on the codeLLDB git https://github.com/vadimcn/vscode-lldb
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.
What are some alternatives?
vscode-cpptools - Official repository for the Microsoft C/C++ extension for VS Code.
saito-rust - A high-performance (reference) implementation of Saito in Rust
nvim-dap - Debug Adapter Protocol client implementation for Neovim
proc-macro-workshop - Learn to write Rust procedural macros [Rust Latam conference, Montevideo Uruguay, March 2019]
Clippy - A bunch of lints to catch common mistakes and improve your Rust code. Book: https://doc.rust-lang.org/clippy/
lol-html - Low output latency streaming HTML parser/rewriter with CSS selector-based API
just - 🤖 Just a command runner
rust - Empowering everyone to build reliable and efficient software.
rst - The open source design documentation tool for everybody [Moved to: https://github.com/vitiral/artifact]
quote - Rust quasi-quoting
cargo-linked - Display linked packages for compiled rust binaries
cargo-llvm-cov - Cargo subcommand to easily use LLVM source-based code coverage (-C instrument-coverage).