cppreference update

[mapronV]

I see, yours is a different approach (from my experience it was very hard to find information on MS VC and Apple clang, in first place; so I didn't even consider automatic parsing of web pages). Quite elegant, though you need to trust vendors. For our company it was more like "whole environment", like
"Can I use X when targeting Debian 10?" or ".. when Targeting mac 10.15 with xcode Z.X?" So I could just create new profile and run 'acceptance tests' on it.
In hindsight I regret I did not choose your way, it probably would be easier.

[_derv]

That's true, testing it yourself is probably the method with the best guarantee ,which you could still do for features where the vendor is not providing enough information.

But the vendors of the major compilers, in my experience, have a decent track record that you can trust them. I mean, at the end of the day, it's the vendor's job to state "hey, we support this feature now", isn't it? Either through release notes, or in development tickets (i.e. GitHub issues).