charlesfrye/aoc2022

Solutions to puzzles from Advent of Code 2022

aoc2022

Solutions to (some) puzzles from Advent of Code 2022 in three languages:

• λ Haskell λ, a lazy, declarative functional programming language
• 🦀 Rust 🦀, a safety-conscious systems programming language
• ☕ Javascript + Node + TypeScript ☕, the contemporary full-stack web dev "language"

It uses devcontainers, the containerization tool for VSCode, to separate the three languages from each other and to make the solutions more portable.

aoc2022's Issues

finish automation of setup of node.js+typescript projects

I need to get the equivalent of running eslint --init and selecting my preferred options into the Makefile.

Just doing that command gets us pretty far (but is interactive), then I think need:

npm install eslint-config-standard-with-typescript

and to set the parserOptions.project in the .eslintrc.json, not sure how to do the latter programmatically (without falling back on awk/sed).

According to error messages, would have to drop at least the "dot-notation" rule in order to avoid the project setting, not sure how standard that is

answer.sh does not run in node.js copied dirs

i believe this is fixable with a chmod in the original file, which gets copied

improve the Haskell setup

I had to pivot to a simpler devcontainer on day 1 because the buildtimes for the more opinionated container were too long

using stack init is a bit much -- it generates changelog, license, readme, etc.

i could just write a quick script to clean the results up and to add make targets for that and for an "environment". if i can get the "name" to be aoc, i can also remove the need to change the executable name for different days

test rust devcontainer on Codespaces

set up Haskell environment

Trying out an unofficial, opinionated one from here.

But build times are long and it installs a lot of stuff -- toolchain and packages -- so may be better to drop back to the official image.

add solution // tests make commands to Node + Typescript template

not sure yet what the solutions will look like -- run a server that responds with answers? -- and don't know the toolchain well enough to know how to do testing

i think the test.sh and test-utils.sh are just for testing the devcontainer, rather than running any "tests" in the project

check setup of rust devcontainer

i may have forgotten to pull in the .vscode directory, which may be why the code command doesn't work

set up Node+Typescript environment

sticking with the official example container, since i don't know this stack