Our best guess is that the two syntaxes should have exactly equivalent effects, so, let's be consistent with what we do in libcxx/include/. I've left `#include "include/x.h"` and `#include "../y.h"` alone because I'm less sure that they're interchangeable, and they aren't inconsistent with libcxx/include/ because libcxx/include/ never does that kind of thing. Also, use the `_LIBCPP_PUSH_MACROS/POP_MACROS` dance for `<__undef_macros>`, even though it's technically unnecessary in a standalone .cpp file, just so we have consistently one way to do it. Differential Revision: https://reviews.llvm.org/D119561
30 lines
715 B
C++
30 lines
715 B
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
|
|
//
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
#include <functional>
|
|
|
|
_LIBCPP_BEGIN_NAMESPACE_STD
|
|
|
|
namespace placeholders
|
|
{
|
|
|
|
const __ph<1> _1{};
|
|
const __ph<2> _2{};
|
|
const __ph<3> _3{};
|
|
const __ph<4> _4{};
|
|
const __ph<5> _5{};
|
|
const __ph<6> _6{};
|
|
const __ph<7> _7{};
|
|
const __ph<8> _8{};
|
|
const __ph<9> _9{};
|
|
const __ph<10> _10{};
|
|
|
|
} // placeholders
|
|
|
|
_LIBCPP_END_NAMESPACE_STD
|