hikari_no_yume
hikari_no_yume
I like how it goes with `list`. `object` takes the scope produced by a function and transforms it into an object. `list` takes the stack produced by a function and...
Just using a succession of key-value pairs could work too, sure. Also not sure about lookup. If an object call be called like a function can, then `/colour mycircle.` works,...
That is a good question. It mostly comes down to whether objects would be immutable, and so you'd create a new object with something changed, or mutable, so you'd modify...
I'm not actually sure about how methods should work, or if we should even have them. They don't seem too elegant so far, and you'd end up having to do...
You could have utility functions to make that specific one simpler. Like `update`, say, which might take a function: ``` firth /x circle [ 10 add. ] update. ``` That...
No, it'd work like it does everywhere else. It's local to that scope.
Oh uh, just to be clear, yes you could do methods. I'm just not sure about using them for object manipulation at the moment. We don't do it for other...
Yeah, I have the same issue with them. Lots of global functions is a problem. We'll see.
The type and the `list` function are already in the spec, I just haven't gotten round to adding functions to manipulate them, and I haven't implemented `list` yet. Same thing...