The library developer doesn't know what allocator will be passed, and the library user doesn't necessarily know how it will be used. They share an interface, so it will [probably] work, but it might not behave (mem/perf wise) as either expects. ArenaAllocators in particular don't play great with ArrayLists or nested ArenaAllocators.
I don't think it's a huge problem, but it's more subtle than an explicit allocator is a better because it provides more flexibility.
Zig seems to be laser focused on systems programming domains where there is value in keeping unusually tight control over everything the program does. Aside from tinkering with Arduino, never been me. If it were, though, then I would probably not want to use a library that wants to be able to arbitrarily grow ArrayLists. I would probably want to structure my program so that it acquires pages of memory (actual memory, not just overcommit) in as few places as possible - ideally one - and from a location very close to the entry point. And a library that doesn’t play nice with that wouldn’t be much more palatable than a library that wants to bring its own memory management runtime along for the ride.
I don’t think that’s totally unreasonable? It’s more restrictive than what most of us are used to, sure. But it’s also quite a bit less restrictive than completely banning dynamic heap allocation as is common in aerospace applications.
Who's angry about how people are spending their already-taxed income? Is that really a thing? Is it sincere or just racism masked as "think of the economy"? (Honest question, Not American. Don't live there, news to me).
The big beautiful bill included a 1% foreign remittance tax for outbound international transfers funded using physical cash, money orders, and cashier's checks.
Which notably, doesn’t affect money transfers in general, just ways that poor people transfer money, so the concern as stated is not in good faith at all, but rather a way to further punish migrant workers, primarily Mexicans, and is absolutely racial animosity.
Oh yes, "sound" and "prudent" haven't been in the ballpark nearly as often as they used to be :(
The dictionary definition is in spite of the fact that the phrase "common sense" is more often than ever being used to rebrand what was formerly known as "common lack of sense".
"If a story is spam or off-topic, flag it. Don't feed egregious comments by replying; flag them instead. If you flag, please don't also comment that you did."
Felt it ~600KM away in a high floor, building was swaying. Others didn't feel it and at first I thought I was just [unusually] light-headed or something, but then we realized a door was swinging back and forth slightly, and a hanging plant was swaying.
I also dislike his self-promotion, but his work _is_ well know and, as far as I know, well looked upon. I think he has more expertise and knowledge in this area than most (including what you'd find in the news).
Ahh, thanks, that explains things a little more. I wasn't familiar with the author, and his tweet just read like one of those people on Linkedin who regurgitates knowledge and passes it off as their own insight.
I don't think it's a huge problem, but it's more subtle than an explicit allocator is a better because it provides more flexibility.
reply