https://github.com/bmatcuk/adventofcode2019
Implementations of the 2019 Advent of Code in rust :christmas_tree:
https://github.com/bmatcuk/adventofcode2019
adventofcode2019 rust
Last synced: 6 days ago
JSON representation
Implementations of the 2019 Advent of Code in rust :christmas_tree:
- Host: GitHub
- URL: https://github.com/bmatcuk/adventofcode2019
- Owner: bmatcuk
- License: mit
- Created: 2019-12-02T14:29:54.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2019-12-25T16:51:46.000Z (over 5 years ago)
- Last Synced: 2025-01-05T22:27:51.848Z (6 months ago)
- Topics: adventofcode2019, rust
- Language: Rust
- Homepage: https://adventofcode.com/2019
- Size: 168 KB
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Advent of Code, 2019 :christmas_tree:
My implementations of the [2019 Advent of Code] puzzles in [rust].
I like to use the Advent of Code as a learning opportunity. This year, I
decided on learning [rust]. I've had a little experience with the language
before AoC, but I really wanted to dive deeper into it.
Because I'm using this as an opportunity to learn rust, I've avoided any
external dependencies. I'm sure some of these puzzles could have been greatly
simplified by pulling in some external crate, but then I would be doing myself
a disservice.
As another benefit, my solutions are completely self-contained. Each day is in
their associated directory, and, within those directories, are `part1.rs` and
`part2.rs` files to solve the parts. These files have no external dependencies
whatsoever, not even to my own code. So, for someone who is having trouble
solving an AoC puzzle, you won't have to hunt around my repo or read crate
documentation to understand my solution; everything is in one file... though, I
can't speak much to my code quality =)
:snowman:
[2019 Advent of Code]: https://adventofcode.com/2019
[rust]: https://www.rust-lang.org/