vasama

> The advantage being that you never have to remember which things are to be freed at which particular error state.

You also don't have to remember this when using defer. That's the point of defer - fire and forget.

That's sort of like asking a motorbike enthusiast why they don't just drive a car instead.

There's a big difference in the input scheme between PC and consoles. Playing with a controller might not be satisfying for someone used to keyboard and mouse. The latter also provides a higher skill ceiling for competitive play.

The lower end hardware used in consoles also does not allow for high framerates and high resolution monitors, while with PC gaming one can get as much performance as they're willing to pay for.

You were clearly banned for the comment where you used offensive slurs in reference to the author of a previously discussed blog post. I was happy to report the comment.

ztd.text is a C++ library. cuneicode is a C library.

If only Linux offered a half decent kernel API instead of that dumpster fire that is POSIX. Even so, for anything not involving graphical user interfaces I somewhat agree with you.

That looks like an allocating container. Probably the most useful property of linked lists and other node based data structures is the ability to make them intrusive and to avoid dynamic allocation. In some domains you just don't have a runtime allocator available to you, so this library would be useless.

If by "STL" you mean the standard library, it's not true that _all_ containers accept allocators. At least valarray and filesystem::path do not accept allocators.

There's no reason to avoid static functions. It's just a better syntax and it's a shame it cannot be applied to class declarations as well.

Molten salt fuel cycles where waste products may be separated from the liquid fuel through more conventional chemical separation methods seem like a simpler solution. It's too bad about the negative public view on nuclear. I think next gen fission power research deserves greater funding.

Nuclear fuels such as U235 are radioactive but very slightly so, U235 specifically having a half life of roughly 700 million years. The various fission products produced by splitting these atoms in a reactor may have much shorter half lives and as such are more radioactive. In the operation of a reactor, some atoms inevitably absorb neutrons as well, which increases their mass number. Through subsequent beta decay whereby a neutron is converted into a proton, their atomic numbers may also increase, producing transuranic elements such as plutonium which account for some of the nastiest nuclear waste products.

The information is indeed worthless unless the standard were to also define such things as the stack layout and a closed set of operations which are allowed to consume more stack, such as defining a VLA, or calling a function.

Whatever values these functions returned, there would be no way for you to make a determination on whether another step can be performed.

Just like with the mutex, this piece of information is out of date as soon as it reaches you. Preparations for whatever action you perform after, or the very act of retrieving this information may invalidate it.

I believe we were discussing a potential addition to the C standard. It would however be useless unless the standard also defined such things as stack layout and a closed set of operations which may consume more stack space, such as calling a function.

There is no useful way to employ these functions. It's equivalent to asking if a mutex is locked. That piece of information is worthless.