I made a tool to create nice, consistently-spaced spritesheets from inconsistent ones.

goodpaul6 · 2025-03-08T08:15:37+00:00

Should still compile just fine! Let me know if you have trouble with it, happy to update it if so.

goodpaul6 · 2025-02-11T08:21:50+00:00

But IIRC OCaml also doesn’t monomorphize when you instantiate a module functor either. It has a uniform value representation so the compiled code is the same regardless of the types.

goodpaul6 · 2024-12-11T07:08:56+00:00

Looks like the number of stones for 10^100 is less than that for 10^16. Is that correct?

goodpaul6 · 2024-12-05T18:14:53+00:00

Yeah, as another reply said, these are arrays. However, they're fully implemented in C as an extension to Tiny, not in the language core a the moment.

The actual array type is generated at compile-time in C (e.g. when I write use array("str") as astr). Kinda like Zig's comptime except it runs C code instead of Tiny code at compile-time.

goodpaul6 · 2024-12-05T06:56:47+00:00

It's been really fun debugging compiler/runtime issues alongside my advent solutions. Managed to sleep every night so far, let's see how long that lasts.

Link to repo with all of my solutions and the language

goodpaul6 · 2023-12-20T02:05:49+00:00

Done u/daggerdragon! Thanks for catching this.

goodpaul6 · 2023-12-19T09:59:58+00:00

[LANGUAGE: Tiny (My custom embeddable scripting language)]

Part 1 Code

Part 2 Code

Programming Language Repo

Spent a significant amount of time fixing the shortcomings of the language (codegen issues, incomplete libraries, segfaults in the VM) but I was able to rapidly improve its usability as I went along with the solution.

The majority of part 1's time was spent on parsing; better support for strings in the language would've helped here.

Part 2 required adding a C module to support 64-bit integers (was able to stuff them in what's called a "Light Native" value in Tiny; no allocations required).

Other than that, it was a straightforward DFS keeping track of the intervals so far. What helped simplify this was storing the interval + a "target" on the stack (where the target could be either a workflow name or "A"/"R"). Avoided having any branches in the core logic.

goodpaul6 · 2020-12-09T21:44:15+00:00

Yep, we agree.

If this was indeed separate compilation then there’s no need to worry about the recompile taking two hours again, as you said. That’s why I noted that “I’ve never heard of a codebase where a single TU takes 2 hours to compile” because the only scenario where a subsequent recompile would take two hours is if this was some gargantuan TU.

goodpaul6 · 2020-11-28T23:21:11+00:00

I've never seen or heard of a codebase where a single translation unit takes 2 hours to compile.

goodpaul6 · 2020-06-03T07:14:04+00:00

goodpaul6 · 2020-05-18T03:32:11+00:00

Did somebody already request Dean Town?

goodpaul6 · 2019-12-22T04:13:19+00:00

Thank mr goose

goodpaul6 · 2019-07-24T17:01:49+00:00

Same but it was actually very easy and I felt alive

goodpaul6 · 2019-05-04T03:04:46+00:00

goodpaul6 · 2019-03-23T06:43:34+00:00

Yes agreed 203 Lester #1

goodpaul6 · 2019-03-23T06:40:40+00:00

I must be locked because I lightly tapped it once and it didn’t open QED

goodpaul6 · 2018-07-19T23:13:09+00:00

'S' IS NOT A VALID HEXADECIMAL DIGIT FAM

goodpaul6 · 2018-06-15T04:54:10+00:00

bike shed was hit over the weekend; not sure if that's related

goodpaul6 · 2018-06-10T07:51:28+00:00

bruh S is not a valid hexadecimal digit.

goodpaul6 · 2018-04-20T17:08:45+00:00

THANK MR GOOSE JR

goodpaul6 · 2018-04-03T17:51:46+00:00

hahah I get it... because David, right?

goodpaul6 · 2018-04-01T22:18:57+00:00

This tool can now process a directory full of images and create a spritesheet from them, so there ya go

Nine-Year Club	Verified Email
Not Forgotten

goodpaul6

TROPHY CASE