There is also a predictable relation between the input and output of a compiler w.r.t. the semantics of a programming language. Natural languages are ambiguous leaving room for the implementation to diverge that may not be obvious at first glance.
There are also plenty of things a compiler might not expose that end up being ambiguous. For example, C++ doesn't officially have a restrict keyword, so how can you express the fact that two memory regions never operlap and can be optimized? Unfortunately the reality is that if we had a language capable of truly expressing the programmer's intent we'd end up with a monster
Up until ~1800, the way societies handled this kind of depravity was to hit the bad actors with sticks or rocks until their skull opened up so the evil spirits could leave their bodies.
It's unfortunate that most societies have outlawed this practice. I'm certain if that were in place today, we wouldn't have this problem.
I've yet to hear any alternative solution that's as effective.
They don’t hand write it because it would be an embarrassment. At the same time, Claude Code doesn’t really need to be any better than it is while Anthropic has great models no one else has.
That's why. That future is uncertain. So why gamble your future on something that's popular at the moment for something that could change completely a year later?
A language without a large stdlib pushes this that functionality into (transitive) dependencies. I hope more language will adopt batteries included approach.
No stdlib will ever include all the "batteries" you need. And large stdlibs have their own set of problems, like stagnation, tying the library version to the language version, backwards compatibility garantees preventing evolution, and either needing a wide range of domain experts to maintain it, or having developers maintain components they don't have a deep understanding of.
I think the sweet spot is having an ecosystem of "blessed" libraries that are reviewed for security and quality, but are versioned independently of the language, and maintained by subject matter experts.
This particular crate (arrayref) seems pretty niche, but also doable in std now.
It lets you take a slice `&[T]` and return a slice with a known number of elements`&[T; N]`. tiny-skia was probably using this to get some SIMD optimizations.
reply