
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
42 lines
1.1 KiB
C++
42 lines
1.1 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: c++03
|
|
|
|
// <filesystem>
|
|
|
|
// class path
|
|
|
|
// path(path&&) noexcept
|
|
|
|
#include "filesystem_include.h"
|
|
#include <type_traits>
|
|
#include <cassert>
|
|
|
|
#include "test_macros.h"
|
|
#include "count_new.h"
|
|
|
|
|
|
int main(int, char**) {
|
|
using namespace fs;
|
|
static_assert(std::is_nothrow_move_constructible<path>::value, "");
|
|
assert(globalMemCounter.checkOutstandingNewEq(0));
|
|
const std::string s("we really really really really really really really "
|
|
"really really long string so that we allocate");
|
|
assert(globalMemCounter.checkOutstandingNewEq(1));
|
|
path p(s);
|
|
{
|
|
DisableAllocationGuard g;
|
|
path p2(std::move(p));
|
|
assert(p2.native() == s);
|
|
assert(p.native() != s); // Testing moved from state
|
|
}
|
|
|
|
return 0;
|
|
}
|