Installing the prerequisites

In this file you'll find instructions on how to install the tools we'll use during the workshop.

All of these tools are available for Linux, macOS and Windows users. We'll need these tools to write and compile our Rust code. Important: these instructions are to be followed at home, before the start of the workshop. If you have any problems with installation, contact the team! Ruben and Thibaut will be happy to help you out.

Rust and Cargo: rustup

First we'll need rustc, the standard Rust compiler. rustc is generally not invoked directly, but through cargo, the Rust package manager. rustup takes care of installing rustc and cargo.

This part is easy: go to and follow the instructions. Please make sure you're installing the latest default toolchain.

On Microsoft Windows, rustup might prompt you to install a linker. rustup prompts to install Visual C++ redist

Once done, you can run

rustc -V && cargo -V

The output should be something like this:

rustc 1.67.1 (d5a82bbd2 2023-02-07)
cargo 1.67.1 (8ecd4f20a 2023-01-10)

Visual Studio Code

During the workshop, we will use Visual Studio Code (vscode) to write code in. Of course, you're free to use your favorite editor, but if you encounter problems, you can't rely on support from us.

You can find the installation instructions here:

We will install some plugins as well. The first one is Rust-Analyzer. Installation instructions can be found here Rust-Analyzer provides a lot of help during development and in indispensable when getting started with Rust.

The last plugin we'll use is CodeLLDB. This plugin enables debugging Rust code from within vscode. You can find instructions here:

More info:


We will use Git to fetch the exercises. If you haven't installed Git already, you can find instructions here:

If you're new to Git, you'll also appreciate GitHubs intro to Git and the Git intro with vscode, which you can find here: More info:

Workshop code

Now that everything is installed, you can clone the source code repository. The repository can be found here: If you're used to Git, you can clone the repository any way you like. Alternatively, you can use Visual Studio Code to clone the repository.

Cloning from within Visual Studio Code

You can clone the repository in Visual Studio Code itself. First, open the command panel (Control+Shift+P), and type gitcl.

Navigate to Git: Clone in VS Code

After confirming with Return, you can enter the repository URL

Enter the repository URL

After confirming "Clone from URL" with Return, Visual Studio Code will ask a directory in which to clone the repository. When asked whether to open the newly cloned workspace, you confirm.

Cloning the classical way

For those familiar to Git, you may opt to clone any way you like. Typically, this would involve the Git command line interface, like so:

git clone

Github provides documentation about cloning repositories here:

Trying it out

Now that you've got the code on your machine, navigate to it using your favorite terminal and run:

cd exercises/0-intro
cargo run

This command may take a while to run the first time, as Cargo will first fetch the crate index from the registry. It will compile and run the intro package, which you can find in exercises/0-intro. If everything goes well, you should see some output:

   Compiling intro v0.1.0 (/home/henkdieter/tg/edu/101-rs/exercises/0-intro)
    Finished dev [unoptimized + debuginfo] target(s) in 0.11s
     Running `target/debug/intro`
🦀 Hello, world! 🦀
You've successfully compiled and run your first Rust project!

If Rust-Analyzer is set up correctly, you can also click the '▶️ Run'-button that is shown in exercises/0-intro/src/ With CodeLLDB installed correctly, you can also start a debug session by clicking 'Debug', right next to the '▶️ Run'-button. Play a little with setting breakpoints by clicking on a line number, making a red circle appear and stepping over/into/out of functions using the controls. You can view variable values by hovering over them while execution is paused, or by expanding the 'Local' view under 'Variables' in the left panel during a debug session.