74b9484fd6
This essentially inlines `__make_tuple_types` and simplifies the support code. This significantly simplifies the implementation, since `__make_tuple_types` has multiple features, but the different places that use it only make use of a subset of the features. Inlining it separates concerns better and leads to less code in total.
47 lines
1.3 KiB
C++
47 lines
1.3 KiB
C++
//===----------------------------------------------------------------------===//
|
|
//
|
|
// 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___TUPLE_TUPLE_ELEMENT_H
|
|
#define _LIBCPP___TUPLE_TUPLE_ELEMENT_H
|
|
|
|
#include <__config>
|
|
#include <__cstddef/size_t.h>
|
|
|
|
#if !defined(_LIBCPP_HAS_NO_PRAGMA_SYSTEM_HEADER)
|
|
# pragma GCC system_header
|
|
#endif
|
|
|
|
_LIBCPP_BEGIN_NAMESPACE_STD
|
|
|
|
template <size_t _Ip, class _Tp>
|
|
struct tuple_element;
|
|
|
|
template <size_t _Ip, class _Tp>
|
|
struct tuple_element<_Ip, const _Tp> {
|
|
using type _LIBCPP_NODEBUG = const typename tuple_element<_Ip, _Tp>::type;
|
|
};
|
|
|
|
template <size_t _Ip, class _Tp>
|
|
struct tuple_element<_Ip, volatile _Tp> {
|
|
using type _LIBCPP_NODEBUG = volatile typename tuple_element<_Ip, _Tp>::type;
|
|
};
|
|
|
|
template <size_t _Ip, class _Tp>
|
|
struct tuple_element<_Ip, const volatile _Tp> {
|
|
using type _LIBCPP_NODEBUG = const volatile typename tuple_element<_Ip, _Tp>::type;
|
|
};
|
|
|
|
# if _LIBCPP_STD_VER >= 14
|
|
template <size_t _Ip, class... _Tp>
|
|
using tuple_element_t _LIBCPP_NODEBUG = typename tuple_element<_Ip, _Tp...>::type;
|
|
# endif
|
|
|
|
_LIBCPP_END_NAMESPACE_STD
|
|
|
|
#endif // _LIBCPP___TUPLE_TUPLE_ELEMENT_H
|