cryptocod3

SSS is amazing, though managing shares over a long period (people come and go) and dealing with collusion risk can be rough.

Not really a question, I was just pointing out that "Unauthorised plagiarism" is redundant.

There's authorized plagiarism?

whoosh

"opinions are my own"

  - throwaway449933

Yep, I just had a slice of bread with strawberry jam and brunost on top

10/10

> if there are hallucinations

Plenty. I assumed that the code examples had been cleaned up manually, so instead I looked at a few random "Caveats, alternatives, edge cases" sections. These contain errors typically made by LLMs, such as suggesting to use features that doesn't exist (std.mem.terminated), are non-public (argvToScriptCommandLineWindows) or removed (std.BoundedArray). These sections also surfaces irrelevant stdlib and compiler implementation details.

Correct

Macros and dynamic typic works fine, but performance is terrible for now as it's an AST interpreter. My main focus is going forward will be to finish the vm/jit backend.

There are at least a couple of other Lisps written in Zig, though I'm not sure about the state. One is in the Mal repository, the other was targeting WASM iirc.

The language supports both (λ is just an alias... which I might remove)

Replaced the example with lambda - appreciate the feedback!

Bio dev here, time to create a HN account I guess. Got a nod that someone posted about it here, which I would prefer to happen a few years from now given the early stage, but hey what can you do :)

I 100% agree with formatting and I've started fixing it, the leftovers were from some (misguided) experimenting.