31cbe0f240
C++98 and C++03 are effectively aliases as far as Clang is concerned. As such, allowing both std=c++98 and std=c++03 as Lit parameters is just slightly confusing, but provides no value. It's similar to allowing both std=c++17 and std=c++1z, which we don't do. This was discovered because we had an internal bot that ran the test suite under both c++98 AND c++03 -- one of which is redundant. Differential Revision: https://reviews.llvm.org/D80926
38 lines
1.2 KiB
C++
38 lines
1.2 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
|
|
//
|
|
//===----------------------------------------------------------------------===//
|
|
//
|
|
// UNSUPPORTED: libcpp-has-no-threads
|
|
// UNSUPPORTED: c++03
|
|
|
|
// <future>
|
|
|
|
// class packaged_task<R(ArgTypes...)>
|
|
// template <class F>
|
|
// packaged_task(F&& f);
|
|
// These constructors shall not participate in overload resolution if
|
|
// decay<F>::type is the same type as std::packaged_task<R(ArgTypes...)>.
|
|
|
|
#include <future>
|
|
#include <cassert>
|
|
|
|
struct A {};
|
|
typedef std::packaged_task<A(int, char)> PT;
|
|
typedef volatile std::packaged_task<A(int, char)> VPT;
|
|
|
|
|
|
int main(int, char**)
|
|
{
|
|
VPT init{};
|
|
auto const& c_init = init;
|
|
PT p1{init}; // expected-error {{no matching constructor}}
|
|
PT p2{c_init}; // expected-error {{no matching constructor}}
|
|
PT p3{std::move(init)}; // expected-error {{no matching constructor for initialization of 'PT' (aka 'packaged_task<A (int, char)>')}}
|
|
|
|
return 0;
|
|
}
|