RustOwl visualizes ownership movement and lifetimes of variables. When you save Rust source code, it is analyzed, and the ownership and lifetimes of variables are visualized when you hover over a variable or function call.
RustOwl visualizes those by using underlines:
- 🟩 green: variable's actual lifetime
- 🟦 blue: immutable borrowing
- 🟪 purple: mutable borrowing
- 🟧 orange: value moved / function call
- 🟥 red: lifetime error - diff of lifetime between actual and expected
Currently, we offer VSCode extension, Neovim plugin and Emacs package.
For these editors, move the text cursor over the variable or function call you want to inspect and wait for 2 seconds to visualize the information.
We implemented LSP server cargo owlsp
with an extended protocol.
So, RustOwl can be used easily from other editor.
Here we describe how to start using RustOwl with VSCode.
curl
,rustup
andcargo
installed- Visual Studio Code (VSCode) installed
We tested this guide on macOS Sequoia 15.2 on arm64 architecture with VSCode 1.96.4 and rustup
1.27.1.
We also tested this guide on Ubuntu 25.04 on arm64 architecture with VSCode 1.96.4 and rustup
1.27.1.
On Ubuntu, you need to run apt install build-essential
before installing.
After installation, the extension will automatically run RustOwl when you save any Rust program in cargo workspace. The initial analysis may take some time, but from the second run onward, compile caching is used to reduce the analysis time.
We tested on Windows 11 Education 23H2 on amd64 architecture. For Windows, please clone this repository and build RustOwl manually.
To install RustOwl command, run the command below.
curl -L "https://github.com/cordx56/rustowl/releases/download/v0.1.2/install.sh" | sh
You can install VSCode extension from this link.
Also, you can download VSCode extension file ( .vsix
) from this link.
We support Neovim and Emacs. You can also create your own LSP client.
Add to plugin manager:
{ "cordx56/rustowl", dependencies = { "neovim/nvim-lspconfig" } }
Configure example:
lspconfig.rustowl.setup {
trigger = {
hover = false,
},
}
keymap(
"n",
"<c-o>",
require("rustowl").rustowl_cursor,
{ noremap = true, silent = true }
)
Elpaca example:
(elpaca
(rustowlsp
:host github
:repo "cordx56/rustowl"
:files (:defaults "emacs/*")))
Here, we describe manual install instructions from source code.
rustup
andcargo
installed- You can install
rustup
from this link. - You need to set up the
PATH
environment variable. To do this, follow the instructions provided by therustup
installer. For example, in bash, runexport PATH=$HOME/.cargo/bin:$PATH
.
- You can install
RustOwl has been tested on macOS Sequoia 15.2 on arm64 architecture with rustup
1.27.1.
We have not tested the installation of dependencies from other package repositories, such as Homebrew.
You may need to uninstall any Rust-related packages installed through those repositories first.
Other dependencies are locked in the configuration files and will be installed automatically.
We have also tested this on Ubuntu 25.04 on arm64 architecture with rustup
1.27.1.
Additional dependencies may be required.
We have confirmed that running apt install build-essential
is necessary on a freshly installed Ubuntu for linking.
cd rustowl
cargo install --path . --locked
cargo owlsp
- VSCode installed
- You can install VSCode from this link.
- Node.js installed
yarn
installed- After installing Node.js, You can install
yarn
by runningnpm install -g yarn
.
- After installing Node.js, You can install
VSCode extension has been tested on macOS Sequoia 15.2 on arm64 architecture with Visual Studio Code 1.96.4, Node.js v20.16.0, and yarn
1.22.22.
Other dependencies are locked in the configuration files and will be installed automatically.
First, install the dependencies.
cd vscode
yarn install --frozen-lockfile
Then open vscode
directory in VSCode.
A notification to install the recommended VSCode extension will appear in the bottom right corner of VSCode. Click the install button, wait for the installation to finish, and then restart VSCode.
Open vscode
directory again, and press the F5
key in the VSCode window.
A new VSCode window with the extension enabled will appear.
Open cargo workspace directory in the new VSCode window.
When you save Rust files, decoration indicating the movement of ownership and lifetimes will appear in the editor.
In this tool, due to the limitations of VSCode's decoration specifications, characters with descenders, such as g or parentheses, may occasionally not display underlines properly.
Additionally, we observed that the println!
macro sometimes produces extra output, though this does not affect usability in any significant way.