Advent-Of-Code-Polyglot - GitLite

KO | EN

gitlite — search

#react #typescript #go #machine-learning #rust #linux #docker #java #windows #awesome #awesome-list #vue #ios #open-source

Advent-Of-Code-Polyglot

(★ 71)

Examples of "Advent Of Code" solutions in many programming languages.

File Explorer

Download Latest Version (.zip)

- - .editorconfig
.gitignore
README.md

# Installation Guide

1. Get the code

git clone https://github.com/ChrisPenner/Advent-Of-Code-Polyglot

Downloads the entire project code from GitHub to your computer.

cd Advent-Of-Code-Polyglot

Moves into the project folder you just downloaded.

2. Rust

Medium Recommended

Prerequisites

Git Needed to download the project code from GitHub.
Rust (rustup) Installing via rustup also installs cargo.

⚠️ This is a large repository, so this method may point to an internal sub-package rather than the actual core product. Check the full README as well.

cd 2015/rust/04

This project's files live in a subfolder, so move into it first.

cargo build --release

Compiles the Rust project.

cargo run

Builds and then immediately runs the program.

✅ If cargo build finishes without errors, it worked. The executable is created under target/.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

Advent of Code
==============

This is a collection of [Advent of Code](http://adventofcode.com/) solutions in
many different programming languages.

For the uninitiated, [Advent of Code](http://adventofcode.com/) is a series of
programming challenges, a new one is released each day until Dec. 25th.

Each challenge requires thinking in a different way to solve it, and for this
reason it provides an interesting look at how programming languages approach
each problem.

You'll notice that in any given situation, the idiomatic Python way of solving
something will be very different from the Haskell or Lisp way of doing things.

Guidelines
----------

-   Create a Pull Request for any contributions.
-   Feel free to put your name or website in a comment at the top of your
    solution if you like.
-   I won't merge any solutions until a few days after each problem is released
    to allow the dust to settle, don't rush in making your PR's, it's not first
    come first merged.
-   The goal of the project is to see the most idiomatic way to solve each
    problem in a given language, for this reason I will keep only the solution
    which I feel best encapsulates 'idiomatic' code of that language. (Or will
    defer to the community in cases where it is unclear)
-   Please don't include your problem's 'input.txt' or solution, as these are
    different for each person.
-   Please put each solution (part 1 and part 2) into separate files (even if
    there's a bit of code duplication) it makes it easier to figure out what's
    going on.
-   Solutions should be easy to read (even for people who don't know the
    programming language), so include comments explaining your solution and any
    interesting
-   programming language tricks/idioms you're using.
-   In pull requests please follow the established pattern:
-   `year/language-name/day-num/part#.extension`

Don't get too competitive about it, someone else's solution may be accepted instead
of yours, keep working at it and try to be as elegant and idiomatic as possible!

Remember to have fun!!