Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/syrtcevvi/advent-of-code-2023
My solutions of the Advent of Code 2023 in Rust
https://github.com/syrtcevvi/advent-of-code-2023
advent-of-code advent-of-code-2023 advent-of-code-2023-rust aoc aoc2023-in-rust rust
Last synced: 22 days ago
JSON representation
My solutions of the Advent of Code 2023 in Rust
- Host: GitHub
- URL: https://github.com/syrtcevvi/advent-of-code-2023
- Owner: syrtcevvi
- License: gpl-3.0
- Created: 2024-05-13T19:10:09.000Z (6 months ago)
- Default Branch: master
- Last Pushed: 2024-06-08T09:22:39.000Z (5 months ago)
- Last Synced: 2024-06-08T10:34:36.298Z (5 months ago)
- Topics: advent-of-code, advent-of-code-2023, advent-of-code-2023-rust, aoc, aoc2023-in-rust, rust
- Language: Rust
- Homepage: https://adventofcode.com/
- Size: 48.8 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Advent of code 2023. Solved in Rust
![Static Badge](https://img.shields.io/badge/days_solved-9-purple)My [Advent of code 2023](https://adventofcode.com/2023/about) solutions in the Rust programming language.
This repository holds a separate Rust project for each day. Parts of a day can be found in `part_1.rs` and `part_2.rs` files and have *binary* names `part_1` and `part_2` respectively.
Initially (till the day 4) my input-parsers were hand-written (just split, and another split.. and so on). Eventually I started to use the [nom crate](https://docs.rs/nom/latest/nom/) and become so excited of the simplicity it brings to the proccess of parsing arbitrary text, compared to the splitting approach. So, I decided to rewrite previously solved `part_2` with the `nom` and gived a name `part_2_nom.rs` for those files.
Since *day 4* I started to use `nom` initially
# Run solutions
To run a specific part of some day, navigate to the corresponding project folder and run the following:
```
cargo run --release --bin part_1
```
or
```
cargo run --release --bin part_2
```# Timings
*TODO*