throwawaymaths

Exactly. I believe the treasury will continue minting commemorative pennies, which would even not make it "none" and give a stronger argument that "well yeah we are meeting the [numismatic] needs"

What exactly is the law?

Can you show me the statute requiring the treasury department to coin pennies?

Yes, and it's in the article.

Let's not forget that incorporated cities, towns etc are people too

If you're a library writer, then don't make a global allocator. If you aren't, then do whatever you feel like.

if it helps: it's pretty typical to attach the allocator to the object directly, so you dont have to pass it everywhere. for library consumers, just build a global allocator and use that. io will just "have to be passed the annoying way" in libraries (but a consumer can also also easily globalize that).

have you actually been to a talk he's given or are you just aping what other people report?

please remember that the page allocator makes an expensive kernel call on each alloc/free call, so if allocation is frequent you may want at least a bump allocator on top. if you don't mind linking libc, for default use cases, c_allocator might be a better choice, as malloc is a quite battle tested general purpose allocator.

FWIW watson was incredibly racist against scots-irish americans, repeatedly calling them dumb in his lectures. that doesn't necessarily excuse his casual racism, but i would assume he meant to imply that people can overcome their genetic ingroups' statistical predilections

did i read "above and beyond"

sel4 is the example of building a safe C program if you go above and beyond in effort.

It's provably safer than rust, e.g.

How does this scheme of yours work with m/s and seconds.

IIUC, rust would NOT let you do a type checked m/s * s => m, so using the type system for these kinds of games is silly and dangerous (I presume you would have to do the dumb thing and typeconvert to the same type -- e.g.

    (m) (speed * ((m/s) seconds))

to do multiplication which means you're inserting unscientific and reader-confusing type conversions all over the place)

iiuc zig has thought about this specifically and there is a safe async-cancel in the new design that wasn't there in the old one.

yes indeed true. but the standard library is in the end just a library, you could reimplement the "pre-io" patterns in the new std if you wanted.

> So how else do you propose we compare countries

dCO2/dt

> If you allocate too much stack in advance, you end up being not much cheaper than OS threads;

Maybe. a smart event loop could track how many frames are in flight at any given time and reuse preallocated frames when their frames dispatch out.

hidden control flow means no control flow occurs outside of function boundaries, keywords, short circuiting operators, or builtins. i believe there is a plan for a asyncresume and asyncsuspend builtins that show the actual sites where control flow happens.

i think you are missing that a proper io interface should encapsulate all abstractions that care about asynchrony and patterns thereof. is that possible? we will find out. It's not unreasonable to be skeptical but can you come up with a concrete example?

> As a library author, how do I handle an io object that doesn't behave as I expect

you ship with tests against the four or five default patterns in the stdlib and if anyone wants to do anything substantially crazier to the point that it doesnt work, thats on them, they can submit a PR and you can curbstomp it if you want.

> function coloring

i recommend reading the function coloring article. there are five criteria that describe what make up the function coloring problem, it's not just that there are "more than one class of function calling conventions"

or you can pick one manually. Or, you can pick more than one and use as needed in different parts of your application. (probably less of a thing for IO than allocator).

I would say zig is not just packed full of great ideas, there's a whole graveyard of ideas that were thrown out (and a universe of ideas that were rejected out of hand). Zig is full of great ideas that compose well together.

Yeah currently the biggest source of oceanic plastic is phillipines IIRC

There are import corrected CO2 emissions data you can check if you care. Tl;Dr it's not as big as you think it is.

You should check the stats on that, it is not the case.

The earth doesn't give a shit about per capita, and us and eu are net reducing CO2 emissions since 2014 (even during trump I)

No but there's an advantage against small and midsized corps

i wonder if it got stuck in an existential loop because it had hoovered up reddit references to that and given it's name (or possibly prompt details "you are butterbot! eg) thought to play along.

are robots forever poisoned from delivering butter?

Actually that seems exactly wrong. unless you set temperature 0, converting logits to tokens is a random pull. so in principle it should be possible for an llm to recognize that it's being asked for a random number and pull tokens exactly randomly. in practice it won't be exact, but you should be able to rl it to arbitrary closeness to exact

the point of all this io stuff is that you'll be able to start playing with zig before async comes and when async comes it will be either drop in if you choose an async io for main() or it will be a line or two of code if you pick an event loop manually.

i mean it might be a medical emergency but not a reactor emergency?