Comment by 🚀 clseibold
Slices are a no-brainer imo, and every language should have them, although I prefer Odin's approach of not storing a capacity in them and instead just a length, which means you always have to allocate a separate backing store before getting a slice, and you can't just resize a slice like in Golang. Instead, you resize the backing store. Odin also makes dynamic arrays a *distinct* type so there's no conflation like what's happening with Hare's proposal.
Linear types are interesting and kinda weird at the same time. The others are meh.
Allocation errors are not exactly groundbreaking nor exciting. I'm surprised Hare has taken this long to add them in, lol. Like, WTH were they thinking aborting on allocation errors? That's insane!
But then again, the Hare devs also choose not to support Windows *and* macOS officially, which is yet another insane thing for a programming language, of all things, to do.
🚀 clseibold [🛂 Code of Conduct rule 1 violations]
2025-06-04 · 11 months ago
Original Post
New blog post — Personally, I always found abort on allocation error annoying and find nomem to be an elegant solution. I am a bit less enthusiastic about the other proposals, although they all make some sense to me.