1.Open[the template repository](https://github.com/fspoettel/advent-of-code-rust) on Github.

2.Click[Use this template](https://github.com/fspoettel/advent-of-code-rust/generate) and create your repository.

3.Clone your repository to your computer.

4.If you are solving a previous year's advent of code, change the`AOC_YEAR` variable in`.cargo/config.toml` to reflect the year you are solving.

1. Open[the template repository](https://github.com/fspoettel/advent-of-code-rust) on Github.

2. Click[Use this template](https://github.com/fspoettel/advent-of-code-rust/generate) and create your repository.

3. Clone your repository to your computer.

4. If you are solving a previous year's advent of code, change the`AOC_YEAR` variable in`.cargo/config.toml` to reflect the year you are solving.

1.Install the[Rust toolchain](https://www.rust-lang.org/tools/install).

2.(recommended) Install the[rust-analyzer](https://rust-analyzer.github.io/manual.html) extension for your code editor.

3.(optional) Install a native debugger. If you are using VS Code,[CodeLLDB](https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb) is a good option.

1. Install the[Rust toolchain](https://www.rust-lang.org/tools/install).

2. (recommended) Install the[rust-analyzer](https://rust-analyzer.github.io/manual.html) extension for your code editor.

3. (optional) Install a native debugger. If you are using VS Code,[CodeLLDB](https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb) is a good option.

1. Install[`aoc-cli`](https://github.com/scarvalhojr/aoc-cli/) via cargo:`cargo install aoc-cli --version 0.12.0`

2. Create an`.adventofcode.session` file in your home directory and paste your session cookie. To retrieve the session cookie, press F12 anywhere on the Advent of Code website to open your browser developer tools. Look in_Cookies_ under the_Application_ or_Storage_ tab, and copy out the`session` cookie value.[^1]

Once installed, you can use the[download command](#download-input--description-for-a-day) and automatically submit solutions via the[`--submit` flag](#submitting-solutions).

Go to the_Secrets_ tab in your repository settings and create the following secrets:

-`AOC_USER_ID`: Go to[this page](https://adventofcode.com/settings) and copy your user id. It's the number behind the`#` symbol in the first name option. Example:`3031`.

-`AOC_YEAR`: the year you want to track. Example:`2021`.

-`AOC_SESSION`: an active session[^2] for the advent of code website. To get this, press F12 anywhere on the Advent of Code website to open your browser developer tools. Look in your Cookies under the Application or Storage tab, and copy out the`session` cookie.

-`AOC_USER_ID`: Go to[this page](https://adventofcode.com/settings) and copy your user id. It's the number behind the`#` symbol in the first name option. Example:`3031`.

-`AOC_YEAR`: the year you want to track. Example:`2021`.

-`AOC_SESSION`: an active session[^2] for the advent of code website. To get this, press F12 anywhere on the Advent of Code website to open your browser developer tools. Look in your Cookies under the Application or Storage tab, and copy out the`session` cookie.

Go to the_Variables_ tab in your repository settings and create the following variable:

-`AOC_ENABLED`: This variable controls whether the workflow is enabled. Set it to`true` to enable the progress tracker.

-`AOC_ENABLED`: This variable controls whether the workflow is enabled. Set it to`true` to enable the progress tracker.

✨ You can now run this action manually via the_Run workflow_ button on the workflow page. If you want the workflow to run automatically, uncomment the`schedule` section in the`readme-stars.yml` workflow file or add a`push` trigger.

1.Install[rust-analyzer](https://marketplace.visualstudio.com/items?itemName=rust-lang.rust-analyzer) and[CodeLLDB](https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb).

2.Set breakpoints in your code.[^3]

3.Click_Debug_ next to the unit test or the_main_ function.[^4]

4.The debugger will halt your program at the specific line and allow you to inspect the local stack.[^5]

1. Install[rust-analyzer](https://marketplace.visualstudio.com/items?itemName=rust-lang.rust-analyzer) and[CodeLLDB](https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb).

2. Set breakpoints in your code.[^3]

3. Click_Debug_ next to the unit test or the_main_ function.[^4]

4. The debugger will halt your program at the specific line and allow you to inspect the local stack.[^5]

-[itertools](https://crates.io/crates/itertools): Extends iterators with extra methods and adaptors. Frequently useful for aoc puzzles.

-[regex](https://crates.io/crates/regex): Official regular expressions implementation for Rust.

-[itertools](https://crates.io/crates/itertools): Extends iterators with extra methods and adaptors. Frequently useful for aoc puzzles.

-[regex](https://crates.io/crates/regex): Official regular expressions implementation for Rust.

A curated list of popular crates can be found on[blessred.rs](https://blessed.rs/crates).

Do you have aoc-specific crate recommendations?[Share them!](https://github.com/fspoettel/advent-of-code-rust/edit/main/README.md)

-**Integer overflows:** This template uses 32-bit integers by default because it is generally faster - for example when packed in large arrays or structs - than using 64-bit integers everywhere. For some problems, solutions for real input might exceed 32-bit integer space. While this is checked and panics in`debug` mode, integers[wrap](https://doc.rust-lang.org/book/ch03-02-data-types.html#integer-overflow) in`release` mode, leading to wrong output when running your solution.

-**Integer overflows:** This template uses 32-bit integers by default because it is generally faster - for example when packed in large arrays or structs - than using 64-bit integers everywhere. For some problems, solutions for real input might exceed 32-bit integer space. While this is checked and panics in`debug` mode, integers[wrap](https://doc.rust-lang.org/book/ch03-02-data-types.html#integer-overflow) in`release` mode, leading to wrong output when running your solution.