The C++ implicit lifetime rules are like the antethesis to Effective Types in C.
C probably had that one right. Again...
On this note, a stdlib c++ implementation could probably provide pure interface structures for the underlying system, where the data is internal by type erasure to the public interface struct.
Inside you reintepret_cast the this pointer to it's original data type.
UB? probably.
So you could use safe<int>...
OR
static_cast<unsigned>(x) + 1 < static_cast<unsigned>(x)
Just fucking learn the language oh my lord.
And this is completely void for string literals, if they are not zero-terminated, the compiler is wrong (or you used raw literal strings in C++).
I guess dogfooding is a symbiosis with Conway's Law, in that since the needs of a system or product is reflective on the organization and it's communication boundaries, by using the system or product you are effectively restructuring to align with communications of the customer.
C++: "Leave no room for a lower level language."
Odin: gingerbill.org/article/2026/…
These are the language type tools I have been looking to see for C as well, example: specifying internal calling conventions and other goodies for specific 2% problems that are load-bearing.
C++:
"You can't take the sizeof your type within the {} and use it with static_assert, because the static_assert is evaluated in incomplete-type context."
y tho.
It's the definition of the class.
This is so dumb, why!?
Built-in types should be built-in, no std:: necessary.
CFI is the baseline, no headers required.
If I see a vector of pointers in any code, there better be an insanely good reason for it.
Or it's fired.
Just one line of deduction guide, and no more need to wrap up functions in silly "deleter" structs. C++, the language of mistakes and missed opportunities.
If you wanna keep sizes down, use lambdas instead of function objects (allows sprinkling of keywords too).
CTAD ftw.
Like @ThePrimeagen says: "Choose your hard".
Hard now or hard later.
Echoes sentiments of Marcus Aurelius and other great stoics.
tfw the __builtin_source_location() on gnu uses a type defined in the <source_location> header...
So you can't use the builtin without including a header.
The fuck is the point of *BUILTIN* stuff if you need to include headers???
Absolutely hate forcing in Standard Libraries.
Someone did not read their C++ object model section or the casting rules section.
cppreference's biggest page is probably on casting.
C is pretty cool tho.
Ginger Bill put into words pretty much my feelings every time I write "template <typename T>", look into type_traits or concepts, or the C++ print templates...
Many such cases where the types I want to use have the same interface, and I want some static virtual dispatching.
My new article is finally done:
CTTI is Exponential, RTTI is Linear
gingerbill.org/article/2026/…
youtube.com/watch?v=7fGB-hjc…
What a great video. 90% agree.
Somewhere in there, there is a good language.
