[resources] Add cppreference.com

[Tsche]

Content added

Adds cppreference.com to general resources.

Source URL: https://en.cppreference.com/

[github-actions]

CI report

Commit 720156b

Build

✅ Site built successfully. Download rendered site | logs

Frontend

No matching frontend workflow ran for this change.

Python

No matching python workflow ran for this change.

Other checks

• ✅ Check - Content and Data success. logs
• ✅ Check - YAML success. logs

✅ All completed checks passed.

[term-est]

I really think we should mention that this is heavily based on the Working Draft

[eisenwave]

I really think we should mention that this is heavily based on the Working Draft

Not sure what you mean. cppreference is based on the various standards, and something that's based on the current C++29 working draft would be marked (since C++29). Everything up to at least C++23 is based on published standards.

[term-est]

cppreference is based on the various standards

sure, that's what i mean. i am not discussing which drafts and standards it uses, i am discussing that "it uses these heavily"
the idea is that, this is more of a copy-paste of a highly technical document than an actual human readable reference or a "guide"

[Tsche]

I don't follow. cppreference does have some literal standardese in its articles, but also a lot of easier-to-digest descriptions and an overall more docs-like structure.

Do you have a specific suggestion for the description of this card, @term-est?

FWIW cppreference describes it self as

What is the purpose of this site?

Our goal is to provide programmers with a complete online reference for the C and C++ languages and standard libraries, i.e. a more convenient version of the C and C++ standards.

The primary objective is to have a good specification of C and C++. That is, things that are implicitly clear to an experienced programmer should be omitted, or at least separated from the main description of a function, constant or class. A good place to demonstrate various use cases is the "example" section of each page. Rationale, implementation notes, domain specific documentation are preferred to be included in the "notes" section of each page.

https://cppreference.com/Cppreference:FAQ

[Tsche]

en. should be dropped, the canonical URL is https://cppreference.com/

[term-est]

Something like this, I think it is essential that we mention this

[term-est]

Something like:

Highly technical language and standard-library reference, often closely following or directly quoting standard wording.