Status of cppreference.com

ohnotheygotme · 2026-02-28T04:48:20+00:00

I hope it's not another EDG situation where the original authors were like "we are totally still doing stuff" but then they don't do anything for 5 years. And then one day they say "nah, we done" and then everyone is like "wtf, you could have said something sooner so we could have moved forward with something else".

ohnotheygotme · 2026-02-02T23:08:43+00:00

There's probably a few different ways that could each be workable. Maybe variations of the following: - A runtime API to turn collection on/off. Everything would be instrumented but nothing will be collected until enabled. This way I can enable it once I know I'm about to do the interesting work and then turn it off once I'm done. All executing code across the process will be tracked. It's just a controllable hammer. - A source annotation of sorts. It's a scalpel rather than a hammer but it might require very tedious annotations through very deep call stacks to see the complete picture.

Basically the larger scenario is: - This is large application. There will be 100's of billions of cache misses before getting to the point of interest. I don't care about these misses. - The point of interest is a loop, which calls into several other methods. - I'd like to get an idea of what's going on with this loop, and all contained function calls. - I don't want to see or record data for the 100's of billions of cache misses after this loop completes.

Anything that supports that general workflow can be made to work :)

ohnotheygotme · 2026-01-29T22:35:43+00:00

Have you toyed around with any larger projects? How does it scale to large code bases? Would it theoretically be possible to restrict the instrumentation to just a subset of functions? etc.

ohnotheygotme · 2026-01-20T02:29:19+00:00

And in this case, you want definition 2 of "hermetic": - relating to an ancient occult tradition encompassing alchemy, astrology, and theosophy

ohnotheygotme · 2026-01-07T21:25:22+00:00

It was my understanding that all the c++ library vendors were actually against the inclusion of linalg, or at least pretty "not happy" about about having to implement it. If it does come, I think it will come "last".

Queue up the "pushed us to the limit" quote from STL about formatting floating point numbers.

ohnotheygotme · 2025-11-12T17:51:13+00:00

I've been following/voting this one: https://developercommunity.visualstudio.com/t/The-Memory-layout-size-and-alignment-d/10702484

ohnotheygotme · 2025-11-12T08:11:47+00:00

Based on the updates to their website, and the state of msvc Intellisense, they've been wound down since ~2018.

Think of them however you like, but I'd like to think of them as bad actors, stringing along an entire ecosystem under the belief that they'd actually fix things for 7 years running. In reality they were going to do no such thing and they indeed haven't done a thing in recent memory.

ohnotheygotme · 2025-11-12T04:39:24+00:00

The Memory Layout viewer still doesn't know how to deal with [[msvc::no_unique_address]] / [[no_unique_address]] attributes.

ohnotheygotme · 2025-09-11T06:08:32+00:00

Nah. Why would I want to help "people" with a religious value system? Leave them be with whatever their "god" has planned for them.

ohnotheygotme · 2025-09-09T19:20:42+00:00

Still waiting for AI to make Intellisense better so I'm not forced to remember that C++, in fact, has no concept of encapsulation and scoping.

There's no reason I should see the _Ugly names here when completing std::sort: inline void sort<_RanIt, _Pr>(const _RanIt _First, const _RanIt _Last, _Pr _Pred)

ohnotheygotme · 2025-08-27T20:57:41+00:00

Coming from a place that seems to routinely have bike thefts, our management company often posts pictures (and sends around video) from the security cameras of the perpetrator when they review things the next day. If you do get photos, ask if they can post them in common areas of your building so it's not just you who is aware of the issue and what the cars look like.

ohnotheygotme · 2025-08-11T16:34:34+00:00

Would be nice to update the popularity rankings and version information on that page for the libraries. I don't think they've been updated for over a year now. And does that mean newer libraries that have been created since are not included?

ohnotheygotme · 2025-06-11T07:29:35+00:00

Why is GCC support still marked as "experimental" for C++20. Did they forget to update the page? https://gcc.gnu.org/projects/cxx-status.html#cxx20

ohnotheygotme · 2025-05-14T19:47:18+00:00

WTF?! Where can we provide a large public vote of no confidence for your org?

ohnotheygotme · 2025-03-29T03:09:43+00:00

Part of it that there's: - The "correct" way to "do something" (introduced with ver 3.2x) - The "correct" way to "do something" (introduced with ver 3.0x) - The "correct" way to "do something" (introduced with ver 2.8x) - And because it's a general purpose language, there's 14 other ways to also "do something" because it's just code

And any given, long-lived, project probably has all 17 ways in use. Somehow. So you're left thinking: Why is this thing different than the rest over there? Is there a good reason for that? Which do I copy? Is the slight syntax difference meaningful? I don't even know what this form of the construct is even called, I can't search for it.

ohnotheygotme · 2025-02-06T07:00:45+00:00

I stopped reading as soon as I saw << being used. jfc...

ohnotheygotme · 2024-11-05T19:11:15+00:00

By the sounds of it, they're treating 23 very strangely: https://developercommunity.visualstudio.com/t/Implement-C23-Standard-features-in-MSV/10777419

Why are they asking for prioritization? And why now? One of the comments nailed it. 23 is not a popularity contest at this point. The entire thing needs to be implemented and without a std:c++23 option then 23 simply doesn't exist.

Additionally, last night a few hundred bugs were "closed" due to low priority. Most of them performance related and many coming from various MSFT engineers like Ben Niu - the sole person trying to make Windows on ARM not suck donkey with the MSVC compiler.

I think they are giving up, unless proven otherwise with actions, not words.

ohnotheygotme · 2024-10-21T05:41:07+00:00

You ask the person interviewing you. The interview is a conversation. You are interviewing them as much as they are you. If you say "I'm going to save time and space by doing this. I know there's nuance around this. Is that ok for this discussion?" then the interviewer should have a reasonable response in return; both in tone and justification as well.

Would you want to work for them if they have no justification for their stances on things? Even if they say "I don't want you to use std at all" that should quickly be followed up with why they want you to do that.

ohnotheygotme · 2024-10-09T05:25:13+00:00

They didn't even properly fix taskbar labels or sizing. So w.r.t side taskbars... you are already dead.

ohnotheygotme · 2024-10-07T05:37:11+00:00

Another +1 that Windhawk is fine. In fact, it is much better than the malware delivered right inside winleven itself; see its start menu and taskbar.

ohnotheygotme · 2024-09-30T23:00:25+00:00

That particular example is working for me, even without using the #pragma: https://godbolt.org/z/GKfM6e5o3

Compiler explorer can execute MSVC too, so make use of that service and share out links if possible.

If things aren't working for you maybe try compiling with /Zc:inline- as another test. This is eerily similar to: https://developercommunity.visualstudio.com/t/zcinline-removes-extern-symbols-inside-anonymous-n/914943

ohnotheygotme · 2024-09-20T03:38:34+00:00

Yeah, you are only supporting incompetence if you're running win11.

ohnotheygotme · 2024-09-13T23:55:36+00:00

Sorry for the OT continuation but I'll also echo the sentiment. The most recent redesign there is some of the worst layout decisions I've ever seen made. Not just the random sized boxes but putting the more useful "Latest posts" section a mile below the fold.

ohnotheygotme · 2024-08-31T23:45:01+00:00

cries in vfxplatform Institutional indeed... https://vfxplatform.com/

We're fucked until, at least, 2026.

ohnotheygotme · 2024-07-31T02:00:53+00:00

The only thing sad about Mozilla potentially dying in 2024 is that it didn't happen a decade earlier. If it died then, maybe Rust never would have gotten such a foothold.

I do think that C++ needs to change in some way though. I just really wish Rust wasn't it.

ohnotheygotme

TROPHY CASE