Danny Robson
f6056153e3
This places, at long last, the core library code into the same namespace as the extended library code.
54 lines
1.6 KiB
C++
54 lines
1.6 KiB
C++
#include "../tap.hpp"
|
|
|
|
#include "../iterator.hpp"
|
|
|
|
#include <vector>
|
|
#include <array>
|
|
|
|
|
|
///////////////////////////////////////////////////////////////////////////////
|
|
int
|
|
main (int, char**)
|
|
{
|
|
cruft::TAP::logger tap;
|
|
|
|
// test that iteration across disparate types works as expected.
|
|
//
|
|
// the char array is an important element because it tends to decay to a
|
|
// pointer type unless we're paying careful attention.
|
|
{
|
|
std::vector<int> v_int { 1, 2, 3 };
|
|
std::array<float,3> a_float { 1.1f, 2.2f, 3.3f };
|
|
char c_char[] = { '\0', 'b', 'c' };
|
|
|
|
bool success = true;
|
|
for (auto const &[i, v, a, c]: cruft::izip (v_int, a_float, c_char)) {
|
|
success = success &&
|
|
v_int[i] == v &&
|
|
cruft::equal (a_float[i], a) &&
|
|
c_char[i] == c;
|
|
}
|
|
|
|
tap.expect (success, "izip containers of int, float, and char and an initialiser_list");
|
|
}
|
|
|
|
|
|
// test that the obvious structured binding syntax gives references to
|
|
// the underlying values rather than silently supplying lvalues.
|
|
//
|
|
// we deliberately do not use any type of references in the range loop so
|
|
// that we check the syntax a user is likely to employ actually works.
|
|
// references may not be an obvious consideration.
|
|
{
|
|
const std::array<unsigned,3> src { 0, 1, 2 };
|
|
std::array<unsigned,3> dst { 2, 0, 1 };
|
|
|
|
for (auto [a,b]: cruft::zip (src, dst))
|
|
b = a;
|
|
|
|
tap.expect_eq (src, dst, "copy using structured bindings");
|
|
}
|
|
|
|
return tap.status ();
|
|
}
|