4 Commits

Author	SHA1	Message	Date
Nikolas Klauser	4f15267d3d	[libc++][NFC] Replace _LIBCPP_STD_VER > x with _LIBCPP_STD_VER >= x ... This change is almost fully mechanical. The only interesting change is in `generate_feature_test_macro_components.py` to generate `_LIBCPP_STD_VER >=` instead. To avoid churn in the git-blame this commit should be added to the `.git-blame-ignore-revs` once committed. Reviewed By: ldionne, var-const, #libc Spies: jloser, libcxx-commits, arichardson, arphaman, wenlei Differential Revision: https://reviews.llvm.org/D143962	2023-02-15 16:52:25 +01:00
Louis Dionne	b8cb1dc9ea	[libc++] Make <ranges> non-experimental ... When we ship LLVM 16, <ranges> won't be considered experimental anymore. We might as well do this sooner rather than later. Differential Revision: https://reviews.llvm.org/D132151	2022-08-18 16:59:58 -04:00
Nikolas Klauser	93172c1c2b	[libc++][ranges] Implement ranges::replace_copy{,_if}. ... Co-authored-by: Konstantin Varlamov <varconst@apple.com> Differential Revision: https://reviews.llvm.org/D129806	2022-08-02 22:32:01 -07:00
Konstantin Varlamov	73ebcabff2	[libc++][ranges][NFC] Implement the repetitive parts of the remaining range algorithms: ... - create the headers (but not include them from `<algorithm>`); - define the niebloid and its member functions with the right signatures (as no-ops); - make sure all the right headers are included that are required by each algorithm's signature; - update `CMakeLists.txt` and the module map; - create the test files with the appropriate synopses. The synopsis in `<algorithm>` is deliberately not updated because that could be taken as a readiness signal. The new headers aren't included from `<algorithm>` for the same reason. Differential Revision: https://reviews.llvm.org/D129549	2022-07-12 02:48:31 -07:00