Carl Mäsak

> * "A wizard did it." No, I mean, the function where the error occurred wasn't defined in any source code, but created programmatically somehow. That certainly wouldn't be common,...

It just struck me, as I got an `overargs` error (very frustrating) that, at least in this particular case, the error had _two_ sites where the blame ought to be...

> (The index of the element list in which we found a match.) I'm not sure I like that idea, 2-and-some years later. Who cares about the index? Why make...

> * To what extent should we disallow `export` and `use` on anything but the top level? Should we disallow `use` that runs conditionally, in an `if` statement? After writing...

> * Surely it should still work if exported function `A` uses non-exported value `B`? By what mechanism should that work? What if there's also an unrelated `B` in the...

I just found [Wren's page about its module system](https://wren.io/modularity.html). One refreshing thing is that (as far as I can see) you are forced to state which names you are importing,...

> * There's `export` and `use` [...] Just wanted to come in here to point out that I called it `use` in the OP, but then basically assumed from thereon...

Quoting [this blog post](https://www.duskborn.com/posts/2021-aoc-zig/): > How things are brought in from the standard library or general foreign code is interesting: > > ```zig > const std = @import("std"); > const...

> It seems that "import mechanisms" sometimes import the **module itself** as a namespace, and sometimes just the **exported names** inside of it. [...] Me, I'm somewhat torn between them;...

I'm 12 minutes into [this talk](https://www.youtube.com/watch?v=-RaFcpNiYCo), and realizing two things which I need to write down here: 1. Doing `(import MODULE)` in the REPL should of course work, and do...