
`Gfx::Vector[2,3,4]` are nearly identical implementations. This code redundancy does not follow the DRY (Don't Repeat Yourself) principle leading to possible out-of-sync errors between the classes. Combining these classes into a class template which can be specialized for each needed size makes the differences obvious through `constexpr-if` blocks and `requires` clauses.
39 lines
769 B
C++
39 lines
769 B
C++
/*
|
|
* Copyright (c) 2021, Stephan Unverwerth <s.unverwerth@serenityos.org>
|
|
* Copyright (c) 2022, the SerenityOS developers.
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include "VectorN.h"
|
|
|
|
#include <AK/Error.h>
|
|
#include <AK/Format.h>
|
|
#include <AK/StringView.h>
|
|
|
|
namespace Gfx {
|
|
|
|
template<class T>
|
|
using Vector4 = VectorN<4, T>;
|
|
using FloatVector4 = Vector4<float>;
|
|
using DoubleVector4 = Vector4<double>;
|
|
|
|
}
|
|
|
|
namespace AK {
|
|
|
|
template<typename T>
|
|
struct Formatter<Gfx::Vector4<T>> : Formatter<StringView> {
|
|
ErrorOr<void> format(FormatBuilder& builder, Gfx::Vector4<T> const& value)
|
|
{
|
|
return Formatter<StringView>::format(builder, value.to_string());
|
|
}
|
|
};
|
|
|
|
}
|
|
|
|
using Gfx::DoubleVector4;
|
|
using Gfx::FloatVector4;
|
|
using Gfx::Vector4;
|