I am sorry to inform you that it was #include "assert.h" with a lot of instrumentation for ubsan, asan etc./

I know you've considered this already but possibly you dismissed it too fast: Would it work to compile from source?

I've solved... remarkably many problems this way and, surprisingly, not actually broken anything (This is not because I'm a gentoo fiend, I'm on casual Pop!_OS)

What I'm trying to say is "Please please I want a built-in slice type."

(I want a built-in slice type in C++ too but I'm *almost* ok with itr pairs and/or std::span)

Fun fact: As a challenge I wrote an entire slice library without testing it until the whole thing was done, then ran it through sanitizers to see how many errors would have slipped through.

It was a *fantastic* library.

It was *absolutely useless* because C invariants are fake.

I hate it here

"Describing C in one sentence" like^

peeb

meep

Goes in the same pocket as the wallet so it doesn't have room to move around.

... that is fucking atrotrocious

> They are doing things that have become normal
> but Noonan portrays them as weirdo conformists.
> This shows us Noonan is out of the loop.

Not necessarily, neh? I hope we're not expecting decency from a journalist.

wet

I don't take pen advice from foxes. Grow some opposable thumbs and maybe it'll be relevant

Not in particular but if you'd care to share, I'll look and see if there's anything that immediately scares me away.

go to beep

but you are already fed up

in 5 years you'll be Mad As Hell and Not Gonna Take This Any More

...wait really?

How much hydration are we talking here?

(I thoght it was the other way around! I thought it'd gotten wet, dissolved, then dry, recrystallized, and now it was hard)

lol

lmao even.

"It's cold to walk outside between buildings"

"The north IS cold and we haven't invented hallways! Deal with it!"

Moon. It'll be back any day now.

No! Sometimes I find it and think "...but then what did I put down over THERE?" and go look!

gm

*glibc

blog.qualys.com/vulnerabilit...

libc I believe

Best I can do is a free function in <algorithm> that takes a back inserter.

❌ Professional sports gambling
✅ metaprogaming

Funny, I was looking into this very thing earlier today. I didn't dig deep but the very very top overview was "faster than C++ because pointers aren't allowed to alias, better than C because arrays aren't nonsense."

And then I stopped digging because "yeah that seems plausible."

I swear I follow more than one person on here

8th edition "Pro C# 7 with .NET and .NET Core" by Troelsen and Japiksen, p. 143:

"Simply put, the role of System.ValueType is to ensure that the derived type (...) is allocated on the stack, rather than on the garbage-collected heap."

Second time this type of nonsense has happened to me THIS MONTH

It's 13 years old by now but I just read Lippert's blog on it and I think my response is "I Guess <shrug emoji>"

cursed c# facts

> if they don't leave the function

Wait what I thought that was just a guarantee at all times (except for, like, value types IN classes where they get alloc'd with the clas)

Have I been allocating when I thought I was just on the stack

D: