en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/test/libcxx/transitive_includes/expected.string#de4a57cb [libc++] Re-add transitive includes that had been removed since LLVM 14This commit re-adds transitive includes that had been removed by4cd04d1687f1, c36870c8e79c, a83f4b9cda57, 1458458b558d, 2e2f3158c604,and 489637e66dd3. This should cover almost all the includes that hadbeen removed since LLVM 14 and that would contribute to breaking usercode when releasing LLVM 15.It is possible to disable the inclusion of these headers by defining_LIBCPP_REMOVE_TRANSITIVE_INCLUDES. The intent is that vendors willenable that macro and start fixing downstream issues immediately. Wecan then remove the macro (and the transitive includes) by default ina future release. That way, we will break users only once by removingtransitive includes in bulk instead of doing it bit by bit a everyrelease, which is more disruptive for users.Note 1: The set of headers to re-add was found by re-generating the transitive include test on a checkout of release/14.x, which provided the list of all transitive includes we used to provide.Note 2: Several includes of <vector>, <optional>, <array> and <unordered_map> have been added in this commit. These transitive inclusions were added when we implemented boyer_moore_searcher in <functional>.Note 3: This is a best effort patch to try and resolve downstream breakage caused since branching LLVM 14. I wasn't able to perfectly mirror transitive includes in LLVM 14 for a few headers, so I added a release note explaining it. To summarize, adding boyer_moore_searcher created a bunch of circular dependencies, so we have to break backwards compatibility in a few cases.Differential Revision: https://reviews.llvm.org/D128661 List of files: /llvm-project-15.0.7/libcxx/test/libcxx/transitive_includes/expected.string Mon, 27 Jun 2022 19:53:41 +0000 Louis Dionne <ldionne.2@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/libcxx/test/libcxx/transitive_includes/expected.string#23d6cde1 [libc++] Add a test to pin down the set of transitive public includesA situation that happens fairly often in libc++ is that we remove sometransitive includes in a header (either purposefully or not) and thatends up breaking users. Of course, we want to be able to remove ourtransitive includes, however it's also good to have a grip on thatto know which commit changed what and when. Furthermore, it's goodto accumulate include removals for a couple of releases to avoidbreaking users at every release for this reason.This commit adds a test that should break whenever we remove aninclude. Hence, it should allow us to track which headers includewhich other headers transitively, giving us a traceable way toremove headers.Differential Revision: https://reviews.llvm.org/D128236 List of files: /llvm-project-15.0.7/libcxx/test/libcxx/transitive_includes/expected.string Mon, 20 Jun 2022 21:10:53 +0000 Louis Dionne <ldionne.2@gmail.com>