#chain_mut — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #chain_mut, aggregated by home.social.
-
As a kind of a side note, while working on #pronelang, I realized that I really want certain language-significant atom names to be shorter in order to take advantage of 7-character-or-less optimizations. And those should probably match up with the visible, documented types of the language constructs.
So there's a couple kinds of value chaining the language is intended to support, really two. Immutable chaining, and mutable chaining. The thunk representation of an immutable chain is marked as `#CHAIN_IMM`. And I guess, if I'd got a bit further on features before my current refactoring, mutable chains would have been marked with `#CHAIN_MUT`. It's not the worst, but, egh.
What I eventually realized is that they don't both have to be called "chain." Mutable chaining uses the -> operator, and that kinda looks like a whip! So the immutable `:` ones can be chains, and the mutable ones, whips.
-
As a kind of a side note, while working on #pronelang, I realized that I really want certain language-significant atom names to be shorter in order to take advantage of 7-character-or-less optimizations. And those should probably match up with the visible, documented types of the language constructs.
So there's a couple kinds of value chaining the language is intended to support, really two. Immutable chaining, and mutable chaining. The thunk representation of an immutable chain is marked as `#CHAIN_IMM`. And I guess, if I'd got a bit further on features before my current refactoring, mutable chains would have been marked with `#CHAIN_MUT`. It's not the worst, but, egh.
What I eventually realized is that they don't both have to be called "chain." Mutable chaining uses the -> operator, and that kinda looks like a whip! So the immutable `:` ones can be chains, and the mutable ones, whips.
-
As a kind of a side note, while working on #pronelang, I realized that I really want certain language-significant atom names to be shorter in order to take advantage of 7-character-or-less optimizations. And those should probably match up with the visible, documented types of the language constructs.
So there's a couple kinds of value chaining the language is intended to support, really two. Immutable chaining, and mutable chaining. The thunk representation of an immutable chain is marked as `#CHAIN_IMM`. And I guess, if I'd got a bit further on features before my current refactoring, mutable chains would have been marked with `#CHAIN_MUT`. It's not the worst, but, egh.
What I eventually realized is that they don't both have to be called "chain." Mutable chaining uses the -> operator, and that kinda looks like a whip! So the immutable `:` ones can be chains, and the mutable ones, whips.
-
As a kind of a side note, while working on #pronelang, I realized that I really want certain language-significant atom names to be shorter in order to take advantage of 7-character-or-less optimizations. And those should probably match up with the visible, documented types of the language constructs.
So there's a couple kinds of value chaining the language is intended to support, really two. Immutable chaining, and mutable chaining. The thunk representation of an immutable chain is marked as `#CHAIN_IMM`. And I guess, if I'd got a bit further on features before my current refactoring, mutable chains would have been marked with `#CHAIN_MUT`. It's not the worst, but, egh.
What I eventually realized is that they don't both have to be called "chain." Mutable chaining uses the -> operator, and that kinda looks like a whip! So the immutable `:` ones can be chains, and the mutable ones, whips.