I for one really enjoy the historical anecdotes you get in the "NOTES", "PORTABILITY" or even "BUGS" sections.
But I do realise that my context is mostly recreational, work doesn't really require glueing POSIX commands together.
What's the state of things regarding statement expressions?
Are there any intentions of adding them? I think I've read Meneide make an offhand comment about that.
This is being discussed. It has some weird corner cases and limitations though. But since it is widely used and supported, I think there is a good chance that some harmonized version of it will be standardized.
Does your Wikipedia mirror include media? Text-only wiki seems a bit bleak to me, but including all media would devour so much storage, I just haven't been able to justify using that much of my limited storage space
Programming is moreso based on recursive problem solving. (Most) language does have some recursive structures, but these become quite difficult to think about after just a few levels, and really aren't what you'd normally consider to be "good language", e.g.
> The dog's owner's house's roof's angle's similarity to an equilateral triangle is remarkable.
You've lost me here a little, sorry.
If you have little to no dynamic allocations, meaning all of your memory will be automatic stack memory, then memory management wouldn't be much of an issue to begin with.
But the most common pattern to me seems to be memory that is allocated upfront, and then treated as-if it were automatic in a hot loop, so not reallocated or moved etc., and then deallocated after the hot part is over.
How does GC interfere with these use-cases, because I'd imagine it would only kick in after, when you'd want to deallocate anyway, but do this automatically without you messing up.
Do you know whether that capacity is regularly reinvestigated?
Because if not you could get the certification, wait a couple of years, and then dismantle all infrastructure while still reaping the, if ephemeral, benefits.
