2022-08-02 22:40:13 -07:00
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
//
|
|
|
|
// Part of the LLVM Project, under the Apache License v2.0 with LLVM Exceptions.
|
|
|
|
// See https://llvm.org/LICENSE.txt for license information.
|
|
|
|
// SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
|
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
|
|
|
|
#ifndef _LIBCPP___ALGORITHM_RANGES_NEXT_PERMUTATION_H
|
|
|
|
#define _LIBCPP___ALGORITHM_RANGES_NEXT_PERMUTATION_H
|
|
|
|
|
|
|
|
#include <__algorithm/in_found_result.h>
|
|
|
|
#include <__algorithm/iterator_operations.h>
|
|
|
|
#include <__algorithm/make_projected.h>
|
|
|
|
#include <__algorithm/next_permutation.h>
|
|
|
|
#include <__config>
|
|
|
|
#include <__functional/identity.h>
|
|
|
|
#include <__functional/ranges_operations.h>
|
|
|
|
#include <__iterator/concepts.h>
|
|
|
|
#include <__iterator/sortable.h>
|
|
|
|
#include <__ranges/access.h>
|
|
|
|
#include <__ranges/concepts.h>
|
|
|
|
#include <__ranges/dangling.h>
|
|
|
|
#include <__utility/move.h>
|
2022-09-05 00:01:15 +02:00
|
|
|
#include <__utility/pair.h>
|
2022-08-02 22:40:13 -07:00
|
|
|
|
|
|
|
#if !defined(_LIBCPP_HAS_NO_PRAGMA_SYSTEM_HEADER)
|
|
|
|
# pragma GCC system_header
|
|
|
|
#endif
|
|
|
|
|
[libc++] Fix missing and incorrect push/pop macros (#79204)
We recently noticed that the unwrap_iter.h file was pushing macros, but
it was pushing them again instead of popping them at the end of the
file. This led to libc++ basically swallowing any custom definition of
these macros in user code:
#define min HELLO
#include <algorithm>
// min is not HELLO anymore, it's not defined
While investigating this issue, I noticed that our push/pop pragmas were
actually entirely wrong too. Indeed, instead of pushing macros like
`move`, we'd push `move(int, int)` in the pragma, which is not a valid
macro name. As a result, we would not actually push macros like `move`
-- instead we'd simply undefine them. This led to the following code not
working:
#define move HELLO
#include <algorithm>
// move is not HELLO anymore
Fixing the pragma push/pop incantations led to a cascade of issues
because we use identifiers like `move` in a large number of places, and
all of these headers would now need to do the push/pop dance.
This patch fixes all these issues. First, it adds a check that we don't
swallow important names like min, max, move or refresh as explained
above. This is done by augmenting the existing
system_reserved_names.gen.py test to also check that the macros are what
we expect after including each header.
Second, it fixes the push/pop pragmas to work properly and adds missing
pragmas to all the files I could detect a failure in via the newly added
test.
rdar://121365472
2024-01-25 15:48:46 -05:00
|
|
|
_LIBCPP_PUSH_MACROS
|
|
|
|
#include <__undef_macros>
|
|
|
|
|
2023-02-14 00:56:09 +01:00
|
|
|
#if _LIBCPP_STD_VER >= 20
|
2022-08-02 22:40:13 -07:00
|
|
|
|
|
|
|
_LIBCPP_BEGIN_NAMESPACE_STD
|
|
|
|
|
|
|
|
namespace ranges {
|
|
|
|
|
|
|
|
template <class _InIter>
|
|
|
|
using next_permutation_result = in_found_result<_InIter>;
|
|
|
|
|
2024-08-01 05:54:06 -07:00
|
|
|
struct __next_permutation {
|
2022-08-02 22:40:13 -07:00
|
|
|
template <bidirectional_iterator _Iter, sentinel_for<_Iter> _Sent, class _Comp = ranges::less, class _Proj = identity>
|
|
|
|
requires sortable<_Iter, _Comp, _Proj>
|
|
|
|
_LIBCPP_HIDE_FROM_ABI constexpr next_permutation_result<_Iter>
|
|
|
|
operator()(_Iter __first, _Sent __last, _Comp __comp = {}, _Proj __proj = {}) const {
|
|
|
|
auto __result = std::__next_permutation<_RangeAlgPolicy>(
|
|
|
|
std::move(__first), std::move(__last), std::__make_projected(__comp, __proj));
|
|
|
|
return {std::move(__result.first), std::move(__result.second)};
|
|
|
|
}
|
|
|
|
|
|
|
|
template <bidirectional_range _Range, class _Comp = ranges::less, class _Proj = identity>
|
|
|
|
requires sortable<iterator_t<_Range>, _Comp, _Proj>
|
|
|
|
_LIBCPP_HIDE_FROM_ABI constexpr next_permutation_result<borrowed_iterator_t<_Range>>
|
|
|
|
operator()(_Range&& __range, _Comp __comp = {}, _Proj __proj = {}) const {
|
|
|
|
auto __result = std::__next_permutation<_RangeAlgPolicy>(
|
|
|
|
ranges::begin(__range), ranges::end(__range), std::__make_projected(__comp, __proj));
|
|
|
|
return {std::move(__result.first), std::move(__result.second)};
|
|
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
inline namespace __cpo {
|
2024-08-01 05:54:06 -07:00
|
|
|
constexpr inline auto next_permutation = __next_permutation{};
|
2022-08-02 22:40:13 -07:00
|
|
|
} // namespace __cpo
|
|
|
|
} // namespace ranges
|
|
|
|
|
|
|
|
_LIBCPP_END_NAMESPACE_STD
|
|
|
|
|
2023-02-14 00:56:09 +01:00
|
|
|
#endif // _LIBCPP_STD_VER >= 20
|
2022-08-02 22:40:13 -07:00
|
|
|
|
[libc++] Fix missing and incorrect push/pop macros (#79204)
We recently noticed that the unwrap_iter.h file was pushing macros, but
it was pushing them again instead of popping them at the end of the
file. This led to libc++ basically swallowing any custom definition of
these macros in user code:
#define min HELLO
#include <algorithm>
// min is not HELLO anymore, it's not defined
While investigating this issue, I noticed that our push/pop pragmas were
actually entirely wrong too. Indeed, instead of pushing macros like
`move`, we'd push `move(int, int)` in the pragma, which is not a valid
macro name. As a result, we would not actually push macros like `move`
-- instead we'd simply undefine them. This led to the following code not
working:
#define move HELLO
#include <algorithm>
// move is not HELLO anymore
Fixing the pragma push/pop incantations led to a cascade of issues
because we use identifiers like `move` in a large number of places, and
all of these headers would now need to do the push/pop dance.
This patch fixes all these issues. First, it adds a check that we don't
swallow important names like min, max, move or refresh as explained
above. This is done by augmenting the existing
system_reserved_names.gen.py test to also check that the macros are what
we expect after including each header.
Second, it fixes the push/pop pragmas to work properly and adds missing
pragmas to all the files I could detect a failure in via the newly added
test.
rdar://121365472
2024-01-25 15:48:46 -05:00
|
|
|
_LIBCPP_POP_MACROS
|
|
|
|
|
2022-08-02 22:40:13 -07:00
|
|
|
#endif // _LIBCPP___ALGORITHM_RANGES_NEXT_PERMUTATION_H
|