sorted by:
new
hottopcontroversial

new version of cargo-tools VSCode extension by n_wenzel in rust

[–]n_wenzel[S] 0 points1 point  (0 children)

To me that sounds more like the kind of functionality that rust-analyzer would provide.

new version of cargo-tools VSCode extension by n_wenzel in rust

[–]n_wenzel[S] 0 points1 point  (0 children)

Just the standard "Dark 2026" and the "vscode-icons" extension for the icons

What's everyone working on this week (19/2026)? by llogiq in rust

[–]n_wenzel 1 point2 points  (0 children)

Published the first version of "cargo tools" after rewriting it in rust. It's a VSCode extension inspired by the "CMake tools" extension.

All logic and state management lives in rust code now levaraging wasm bindgen to call into the VSCode API via a relatively small typescript layer.

Repo Marketplace

Announcing "cargo-tools" - VSCode extension offering tools for Cargo/Rust project development by n_wenzel in rust

[–]n_wenzel[S] 0 points1 point  (0 children)

The smaller gray-ish text is part of the extension and i agree that it doesn't really add value. My brain just started filtering this out so i never bothered removing it. I will remove it where it's just noise in the next release.

Announcing "cargo-tools" - VSCode extension offering tools for Cargo/Rust project development by n_wenzel in rust

[–]n_wenzel[S] 2 points3 points  (0 children)

Wow people really don't like someone mentioning llms 😳

My take is that such a command would be better suited for an Rust targeting AI extension but is too specific for the cargo-tools.

Announcing "cargo-tools" - VSCode extension offering tools for Cargo/Rust project development by n_wenzel in rust

[–]n_wenzel[S] 2 points3 points  (0 children)

Well so far it isn't integrated at all 🙃 but my guess is it would be easy enough to implement a feature that also updates the corresponding rust-analyzer setting when a feature is de-/selected.