Update cppreference tag file to latest version

[mcbarton]

Our tag file for Cppreference is very out of date. This PR updates the tag file to the latest version (taken from here https://en.cppreference.com/w/Cppreference%253AArchives.html) which was created by cppreference on 09/02/2025

The huge diff is unavoidable as the tag file is what it is, as I took the tag file verbatim from html-book-20250209/cppreference-doxygen-web.tag.xml and the current one is very out of date.

[anutosh491]

Oh my god I don't know what to do now. The diff is crazy huge 😅

[mcbarton]

Oh my god I don't know what to do now. The diff is crazy huge 😅

I just checked in the PR deployment of xeus-cpp-lite and it didn't solve the problem as I expected. std::move, std::copy, std::sort are mentioned in the tag file so thought this would fix it. It seems the underlying problem is something else, but we may still want the updated tag file so that we have access to documentation from the latest c++ standard.

[mcbarton]

The Emscripten failures seem unrelated since the documention command still works in the xeus-cpp-lite deployment. Can't tell what in the ci is failing, as I find doctest output confusing. Did a xeus-cpp dependency get a new release very recently?

[mcbarton]

The Emscripten failures seem unrelated since the documention command still works in the xeus-cpp-lite deployment. Can't tell what in the ci is failing, as I find doctest output confusing. Did a xeus-cpp dependency get a new release very recently?

I'm also really confused about how this new tag file is causing a Valgrind memory issue 😅. Maybe its related to the Emscripten failures. Maybe the memory leak is causing an error in the Emscripten tests which are more sensitive to such issues.

[mcbarton]

@anutosh491 I think i know the source of the issue getting std::move for example. To look it up in the tag file, its name is not std::move. There are mutliple std::moves in cppreference such as move (utility)

    <member kind="function">
      <type>T</type>
      <name>move (utility)</name>
      <anchorfile>cpp/utility/move</anchorfile>
      <anchor></anchor>
      <arglist>(T... args)</arglist>
    </member>

A second issue is that if you execute ?move (utility) it looks for move, and ignores the (utility) part as far as i can tell. move by itself is the name for something else in cppreference.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.28%. Comparing base (5d57832) to head (414b496).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #458   +/-   ##
=======================================
  Coverage   80.28%   80.28%           
=======================================
  Files          21       21           
  Lines         847      847           
  Branches       78       78           
=======================================
  Hits          680      680           
  Misses        167      167           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mcbarton]

@SylvainCorlay @JohanMabille @vgvassilev @anutosh491 I have detailed the underlying problem of why you cannot find the documentation for things such as std::move in the open issue here #456 (comment) . This PR is now an entirely separate issue, of updating the cppreference tag file to the latest version since xeus-cpps is so out of date.

[JohanMabille]

Let's get this in!