Testing against multiple solutions and multiple input/output-pairs

[Arxcis]

TLDR;

A lot of stuff is changing, but the repo will still be familiar to you 👍

Why?

1. Make it possible for everyone to submit their own input, without worrying about getting conflicts with others.

2. It is helpful to test against multiple distinct input/output-pairs, to make sure our solutions are robust - does not make assumptions about a specific input/output-files being provided.

arxcis.input
arxcis.output
preng.input
preng.output

Suggested change

Change the signature of the language-tests to take a list of SOLUTION_FILES and a list of IO_FILES as input:

Example declaration in languages/go.sh

#!/usr/bin/env bash
set -euo pipefail

# Usage:      ../../lang/go.sh  "SOLUTION_FILES"   "IO_FILES"
#
# Example:    ../../lang/go.sh  "solutions/*.go"   "io/*"
# Expands to: ../../lang/go.sh   solutions/main.go  io/alice.input io/alice.output io/bob.input io/bob.output
#
SOLUTION_FILES=$1   # Expand $1 into list
IO_FILES=$2         # Expand $2 into list

Example usage in days/day-05/test.sh

echo ""
echo "--- Day 5: Boarding pass ---"

$D/../../lang/go.sh     "$D/solutions/*.go"   "$D/io/*"
$D/../../lang/c.sh      "$D/solutions/*.c"    "$D/io/*"
$D/../../lang/sml.sh    "$D/solutions/*.sml"  "$D/io/*"
$D/../../lang/python.sh "$D/solutions/*.py"   "$D/io/*"
$D/../../lang/deno.sh   "$D/solutions/*.ts"   "$D/io/*"

echo ""

Example running ./days/day-05/test.sh

--- Day 5: Boarding pass ---
cat INPUT | go       day05.stektpotet.go     2ms        ✅
cat INPUT | go       tholok97.go             2ms        ✅
cat INPUT | gcc      day05.c                 2ms        ✅
cat INPUT | polyc    day05.sml               4ms        ✅
cat INPUT | python3  day05.klyve.py          15ms       ✅
cat INPUT | python3  day05.preng.py          11ms       ✅
cat INPUT | python3  day05.stektpotet.py     11ms       ✅
cat INPUT | python3  one-liner.stektpotet.py 12ms       ✅
cat INPUT | deno     day05.ts                15ms       ✅

[tholok97]

I'll have a look after work @Arxcis :)

[tholok97]

@Arxcis sorry I got hung up doing aoc with a friend over discord, and then I hit my head against the wall with lisp for a while.. I don't know when I'll have time to take a proper look at this. I have a suggestion, but I don't feel comfortable giving it until I've tried to look for myself how it will work in practice.

(Btw behold my creation:

A precursor to how I want to do day 1 in Lisp)

[Arxcis]

@tholok97 No worries. I have the feeling, I am going to need a few days to settle on something myself. This PR is not currently building in the CI, so you can hold off reviewing, until I have at least figured that one out.

We can do the review/discussion/grooming in IRL if you like 😉 The good thing with this PR, is that we will eventually have something to look at while discussing .

[Arxcis]

You know what. I got a breakthrough. The tests are passing, and I am happy with how the new architecture works. I am comfortable with setting this to "Ready for review" now, as I am going to bed 🛏️ 😴

[Arxcis]

I got a really good review from @tholok97 IRL 😄 Thank you very much! 🙏 I will take all the things into consideration when making a decision on what to do tonight.

[Stektpotet]

From what I saw, only a couple of minor things need to/can be "fixed" here.
As a whole, nice merge 👍

[Stektpotet]

One of the maintainers will merge PR's, at the ................. of each day.

[Arxcis]

👀 Well spotted. Since I already merged, I will commit a fix for this directly 👍

[Stektpotet]

I'm pretty sure most of the readme fiiles we have so far have these two combined.

It could be changed to this:

# --- $DAY: Title ---

Not that that really matters in the template, as it's going to be written over at some point again...
¯\_(ツ)_/¯

[Arxcis]

I think it matters, even if it is a minor thing, because the template is supposed to help the developer. It is a way of documenting things, and communicating intent, so that any contributor is capable of contributing README.md's. I will fix in a commit directly. 👍

[Arxcis]

Thank you for reviewing @Stektpotet 🙏