Ahmed al-Ahmed the GOAT - he went in and disarmed one of the gunmen, absolute chad

wishing him and everyone else injured a speedy recovery

that it, indeed, valid Go (or atleast the general syntax should be right, I wrote it in a scratchpad w/o an LSP)

the formal name for these appear to be "methods" where the `(twln *Thingy)` defines a "receiver"

go.dev/tour/methods/1

sounds good in practice but easier said than done - especially for long or less abbreviable (?) type names, and can be a pain if you need to rename or refactor your code

and yea, the signature syntax is a bit kludgey but my main gripe is that naming it `this` or `self` poses a lint warning :\

in Go, types (including structs) can have free associated functions that can be invoked with dot notation, which require a special separate parameter in the function signature

instead of `this` or `self`, the convention in Go is to use some sort of shortening of the type name itself (continued)

it's a warning, so it doesn't stop the code from compiling

but it is a bit annoying and for some reason the documented steps for disabling the warning didn't work for me

btw `QalcExprString` is just a thin wrapper around `str` that removes the quote marks from the repr, makes the inline output cleaner

i should give it a swankier name than "jahinzee's custom repl environment"

time to switch to Deno?

my goal for this year's AoC isn't pure performance, i'm coming at this from a more general "programming muscle training" angle - do my best, learn something new and have fun along the way

i meant to say that it's got very poor time complexity, even by Python standards - takes a good few seconds at the command-line to return a result from the input file

a quick hyperfine benchmark tells me my code takes about 5.5 seconds to print the result