A Rust code completion utility for editors and IDEs, providing auto-complete and eldoc functionality.
Racer is a Rust code completion utility that provides auto-complete and documentation (eldoc) functionality for Rust developers within their code editors and IDEs. It parses Rust source code to offer intelligent suggestions, helping speed up development and reduce errors. The tool was widely used before being superseded by newer solutions like rust-analyzer.
Rust developers who want enhanced code completion and documentation support in lightweight editors like Vim, Emacs, or Sublime Text, without relying on a full IDE.
Racer offers a simple, editor-agnostic solution for Rust code completion, with broad editor support and easy integration. It was a popular choice before rust-analyzer due to its reliability and minimal setup.
Rust Code Completion utility
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Integrates with a wide range of editors including Vim, Emacs, VS Code, and Sublime Text, as listed in the README, making it versatile for different workflows.
Designed as a minimal utility that doesn't require a full IDE, fitting seamlessly into any editor environment without heavy dependencies.
Can be configured to work with stable, beta, and nightly Rust toolchains, offering flexibility for developers using different release channels.
Shows documentation for code elements directly in the editor, enhancing productivity by providing instant context without switching windows.
The README explicitly states Racer is not actively developed and recommends rust-analyzer, meaning no bug fixes or new features.
Requires nightly Rust from version 2.1, which can be unstable and incompatible with projects locked to stable toolchains.
Involves fetching Rust source code, setting environment variables like RUST_SRC_PATH, and managing multiple toolchains, adding friction to installation.
Completion for external crates only works when Cargo.lock is present, necessitating a build step first, which can slow down workflow.