Rust Code Visualizer (preview)
Write Rust in the browser and preview its structure as flowcharts, call graphs, and module diagrams. Honest disclosure up front: Rust support is currently a preview — the full AST engine that powers our Go visualizer is still in development for Rust.
What works today
- Full editor support —
.rsandCargo.tomlfiles with syntax highlighting, multiple files, and folders. - Preview program flow — functions,
if/matchbranches,for/while/looploops, and returns detected per line. - Preview call graph — function-to-function call edges within your project.
- Preview module graph — files connected through
mod,crate::, andsuper::references.
What the preview does not do
The preview analyzer scans source text without type-checking, so it can
miss or simplify trait dispatch, macros, closures in complex positions,
and ? error propagation. Diagrams are a structural sketch,
not an exact semantic model. When the full Rust engine ships, it will
use proper AST parsing — the same deterministic, no-AI approach as the
Go engine.
Why visualize Rust code?
Ownership, early returns, and deeply nested match arms make
Rust control flow dense to read as text. A diagram shows the branching
structure and call relationships at a glance — useful when learning the
language, reviewing a crate, or explaining a design. You can share any
workspace with a public share link.
FAQ
- Does CodeGraph support Rust?
- Partially: full editor support plus a lightweight preview analyzer. A full Rust AST engine is planned but not implemented yet.
- How accurate is the Rust preview analysis?
- It recognizes functions, calls, branches, loops, returns, and modules line by line, without type-checking. Treat the result as a structural sketch.
- Does CodeGraph execute my Rust code?
- No. Analysis is static and runs in your browser; nothing is compiled or run.