[all-commits] [llvm/llvm-project] 930915: [libc++] Include the full set of libc++ transitive...

[Louis Dionne via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 930915a27a5bc8079de211c96bce15eb2bb18d22
      https://github.com/llvm/llvm-project/commit/930915a27a5bc8079de211c96bce15eb2bb18d22
  Author: Louis Dionne <ldionne.2 at gmail.com>
  Date:   2024-09-10 (Tue, 10 Sep 2024)

  Changed paths:
    M libcxx/test/libcxx/transitive_includes/cxx03.csv
    M libcxx/test/libcxx/transitive_includes/cxx11.csv
    M libcxx/test/libcxx/transitive_includes/cxx14.csv
    M libcxx/test/libcxx/transitive_includes/cxx17.csv
    M libcxx/test/libcxx/transitive_includes/cxx20.csv
    M libcxx/test/libcxx/transitive_includes/cxx23.csv
    M libcxx/test/libcxx/transitive_includes/cxx26.csv
    M libcxx/test/libcxx/transitive_includes_to_csv.py
    R libcxx/utils/graph_header_deps.py

  Log Message:
  -----------
  [libc++] Include the full set of libc++ transitive includes in the CSV files (#107911)

When we introduced the machinery for transitive includes validation, at
some point we stopped including the full set of transitive includes in
the CSV files and instead only tracked the set of public headers
included *directly* by a top-level header.

The reason for doing that was so that the CSV files containing
"transitive" includes could be used to draw the dependency graph of
libc++ headers. However, the downside was that it made the contents of
the CSV files much harder to interpret.

In particular, many changes that modify the CSV files do not in fact
modify the effective set of transitive includes, which is confusing.
This patch goes back to storing the full set of transitive includes in
the CSV files and removes the ability to graph the libc++ includes
directly from those CSV files, which we never actually used.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications