Jon Purdy

We could go more Forthlike, having a dictionary you insert into with `def`. So if you redefine `f`, then old-`f` will be hidden, but definitions pointing to old-`f` will continue...

Like many things, will! :P I have detailed plans for unboxed types, just haven’t finished implementing them, and sadly my most recent code is on a computer that’s out for...

`List` in Kitten isn’t meant to be a linked list, but a size + capacity + pointer to an array, like `List` in C# (`ArrayList` in Java, `std::vector` in C++)....

I’m not sure any particular choice for comment syntax is clearly better than any other, so borrowing C-family syntax seemed reasonable. And I guess the “literate Kitten” approach is cleaner...

Yeah, right now the `->` syntax is parsed in such a way that it introduces a local scope which lasts until the end of the enclosing block. That’s not really...

Ah, right, the type doesn’t need to change. Every function starts with 0 locals and drops all of them at the end; `->` only adds locals. And the `leave` instruction...

How’s it going? Is there anything I can help with?

This is semi-fixed in the new compiler. In top-level code, variable scopes can cross other top-level program elements: ``` "hello" -> x; define f (…) { … } x say...

Well, I don’t like the backticks—accent marks aren’t quotes, and don’t really belong in the language. So this looks better, but I worry that it would overload parentheses too much....

Yeah, I guess I should close or update this to reflect how my thinking and the actual implementation have been evolving. By “GC strategies”, I meant any strategy for collecting...