-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing names #28
Comments
Do you mean pages for things in C++20? This is just an offline clone of cppreference.com, so if a page is not on cppreference.com then it won't be here either. If you're referring to Doxygen tag files, that content gets updated upstream and recent changes will be included with every new release. |
No, I mean things like:
Ok, so I should report missing names upstream? |
So you're talking about tag files? |
Yep, I meant Doxygen tag files. Just, so that there is no confusion:
correct? |
If something is missing from cppreference.com then you can contribute it yourself, there's nowhere to report that (it's a wiki after all). In general: usually you'll want to report any issues with the offline archive at p12tic/cppreference-doc. Anything that's specific to this fork you can report here of course. Specifically Doxygen tag files: you can try and open a ticket upstream, but you might wanna contribute missing entries yourself and open a PR instead ;-) |
It's not about things missing from the Wiki. I already said before that I mean things like the following:
I opened an issue there but got no response so far: p12tic#127
I am not sure what is specific to this port. I inherited a workflow that pulls cppreference-doxygen-web.tag.xml from the html-book from this fork. Is that specific to this port? I could not find these files in the parent repo.
I would be very willing to add things, but I have no clue where/how. |
Thanks for your work on this first of all!
Even the latest release seems to be missing lots of C++20 stuff, like Concepts and things from
std::ranges::
. Is this a known issue?The text was updated successfully, but these errors were encountered: