| .. | ||
| .gitignore | ||
| 1.test.ts | ||
| 1.ts | ||
| 2.ts | ||
| 3.test.ts | ||
| 3.ts | ||
| 6.zig | ||
| common.nim | ||
| common.ts | ||
| common.zig | ||
| deps.ts | ||
| eight.nim | ||
| five.nim | ||
| four.nim | ||
| nine.nim | ||
| one.nim | ||
| readme.md | ||
| seven.nim | ||
| six.nim | ||
| three.nim | ||
| two.nim | ||
2021
This year, I've been tinkering a lot with Deno as a TypeScript runtime and have been really enjoying it. I'm hoping to write this year's AoC solutions using it.
Specifically, here's my deno --version output:
deno 1.16.3 (release, x86_64-unknown-linux-gnu)
v8 9.7.106.5
typescript 4.4.2
Enjoy!
EDIT: Since performance is not what I would like, it looks like I'm also doing some of these in Nim.
EDIT 2: I sprinkled some zig in there. I've been meaning to mess with it for a while.
Usage
Run these solutions like so:
deno run --unstable --allow-all $DAY.ts
And the Nim ones like so:
nim c -d:release -d:ssl --run $DAYMODULE.nim
And the Zig ones like so:
zig build-exe -O ReleaseFast 6.zig -femit-bin=build/zig-$DAY
./build/zig-$DAY
And if you want to measure memory usage with Deno programs:
mkdir -p build
deno compile --output build/$DAY --unstable --allow-all $DAY.ts
/usr/bin/time -v ./build/$DAY
Or for Nim programs:
mkdir -p build
nim c -d:release -d:ssl --outdir:build $DAYMODULE.nim
/usr/bin/time -v ./$DAYMODULE
Or for Zig programs:
mkdir -p build
zig build-exe -O ReleaseFast 6.zig -femit-bin=build/zig-$DAY
/usr/bin/time -v ./build/zig-$DAY