c++ - C++ 20:std::array 作为非类型模板参数重新洗牌元素
问题描述
我最近实现了一个 Builder 类,但我想避免抛出异常。所以我有一个想法,我可以用一组表示已设置哪些字段的布尔值对 Builder 进行参数化。每个 setter 都将返回 Builder 的新特化,并设置了相应的字段标志。这样我就可以检查在编译时是否设置了正确的字段。
事实证明,作为非类型模板参数的复杂数据类型仅在 C++ 20 中可用。但我还是尝试了它。
事实证明,它以一种奇怪的方式行为不端。当返回每个新的特化时,“true”标志会在开始时聚集在一起,如以下示例调试输出所示:
- set field 4 old flags 00000 new flags 00001
- set field 2 old flags 10000 new flags 10100
- set field 0 old flags 11000 new flags 11000
- set field 3 old flags 11000 new flags 11010
- set field 1 old flags 11100 new flags 11100
这些来自下面两行中的第二行。删除第一个解决了问题,表明第一个实例化以某种方式影响了第二个。
Fields fields1 = Builder().SetFirst(1).SetSecond(2).SetThird(3).SetFourth(4).SetFifth(5).Build();
Fields fields2 = Builder().SetFifth(5).SetThird(3).SetFirst(1).SetFourth(4).SetSecond(2).Build();
它应该这样做吗?这只是我以某种方式遗漏的 C++ 20 的一个微妙之处,还是 gcc 中的一个错误?
我用 gcc 9.3.0 和 gcc 10.2.0 检查了这个。我还尝试从 git 编译,版本 11.0.1 更改 a18ebd6c439。命令行是g++ -Wall --std=c++2a builder.cpp
. 它们的行为方式都相同。我还在 gcc 的 bugzilla 中进行了搜索,但找不到任何看起来相似的内容。
下面是两个代码示例。首先,尽可能地剥离一个版本以显示问题。第二个显示了我试图实现的更多背景。(还有第三个更现实的版本,但公开发布可能会有问题。)
#include <array>
#include <cassert>
using Flags = std::array<bool, 2>;
template<Flags flags = Flags{}>
class Builder
{
public:
Builder() {
}
auto SetFirst() {
constexpr auto new_flags = SetFieldFlag<0>();
Builder<new_flags> new_builder;
return new_builder;
}
auto SetSecond() {
constexpr auto new_flags = SetFieldFlag<1>();
Builder<new_flags> new_builder;
return new_builder;
}
Flags GetFlags() const {
return flags;
}
private:
template<int field>
static constexpr auto SetFieldFlag() {
auto new_flags = flags;
std::get<field>(new_flags) = true;
return new_flags;
}
};
int main()
{
auto flags1 = Builder().SetFirst().SetSecond().GetFlags();
assert(flags1[0]);
assert(flags1[1]);
auto flags2 = Builder().SetSecond().SetFirst().GetFlags();
assert(flags2[0]);
assert(flags2[1]);
return 0;
}
#include <iostream>
#include <array>
constexpr int NumFields = 5;
using Flags = std::array<bool, NumFields>;
using Fields = std::array<int, NumFields>;
std::ostream& operator<<(std::ostream& out, Flags flags) {
for (int i = 0; i < NumFields; ++i) {
out << flags[i];
}
return out;
}
std::ostream& operator<<(std::ostream& out, Fields fields) {
for (int i = 0; i < NumFields; ++i) {
out << (i ? ":" : "") << fields[i];
}
return out;
}
template<Flags flags = Flags{}>
class Builder
{
public:
Builder(Fields fields_in = Fields{})
: fields(fields_in) {
}
auto SetFirst(int value) {
fields.at(0) = value;
return BuilderWithField<0>();
}
auto SetSecond(int value) {
fields.at(1) = value;
return BuilderWithField<1>();
}
auto SetThird(int value) {
fields.at(2) = value;
return BuilderWithField<2>();
}
auto SetFourth(int value) {
fields.at(3) = value;
return BuilderWithField<3>();
}
auto SetFifth(int value) {
fields.at(4) = value;
return BuilderWithField<4>();
}
Fields Build() {
std::cout << " - build with flags " << flags << std::endl;
static_assert(std::get<0>(flags), "first field not set");
static_assert(std::get<1>(flags), "second field not set");
static_assert(std::get<2>(flags), "third field not set");
static_assert(std::get<3>(flags), "fourth field not set");
static_assert(std::get<4>(flags), "fifth field not set");
return fields;
}
private:
template<int field>
static constexpr auto SetFieldFlag() {
auto new_flags = flags;
std::get<field>(new_flags) = true;
return new_flags;
}
template<int field>
auto BuilderWithField() {
constexpr auto new_flags = SetFieldFlag<field>();
std::cout << " - set field " << field << " old flags " << flags << " new flags " << new_flags << std::endl;
Builder<new_flags> new_builder(fields);
return new_builder;
}
Fields fields;
};
int main()
{
Fields fields1 = Builder().SetFirst(1).SetSecond(2).SetThird(3).SetFourth(4).SetFifth(5).Build();
std::cout << fields1 << std::endl;
Fields fields2 = Builder().SetFifth(5).SetThird(3).SetFirst(1).SetFourth(4).SetSecond(2).Build();
std::cout << fields2 << std::endl;
return 0;
}
解决方案
I have used https://godbolt.org/ to examine the generated code for multiple compilers and this is indeed a bug in gcc. Both clang and msvc produce correct results.
Here's the interesting part, the assembler generated for the method Builder<std::array<bool, 2ul>{}>::SetSecond()
which causes the error in your shorter example. The actual code is not that important, the error can be seen by looking at the types:
Clang produces (correctly) this:
Builder<std::array<bool, 2ul>{}>::SetSecond(): # @Builder<std::array<bool, 2ul>{}>::SetSecond()
push rbp
mov rbp, rsp
sub rsp, 32
mov qword ptr [rbp - 8], rdi
mov ax, word ptr [.L__const.Builder<std::array<bool, 2ul>{}>::SetSecond().new_flags]
mov word ptr [rbp - 16], ax
lea rdi, [rbp - 24]
call Builder<std::array<bool, 2ul>{bool [2]{false, true}}>::Builder() [base object constructor]
add rsp, 32
pop rbp
ret
GCC produces (incorrectly) this:
Builder<std::array<bool, 2ul>{}>::SetSecond():
push rbp
mov rbp, rsp
push rbx
sub rsp, 40
mov QWORD PTR [rbp-40], rdi
mov WORD PTR [rbp-18], 0
mov BYTE PTR [rbp-17], 1
lea rax, [rbp-19]
mov rdi, rax
call Builder<std::array<bool, 2ul>{bool [2]{true}}>::Builder() [complete object constructor]
nop
mov eax, ebx
mov rbx, QWORD PTR [rbp-8]
leave
ret
If you compare the type of the function that gets call
ed, you can clearly see that in gcc, SetSecond()
did not set the second -- there's {true}
, but should be {false, true}
.
So, time to switch to clang?
推荐阅读
- bash - for循环追加变量bash 6
- python - OSError:请求的地址在其上下文中无效
- java - 如何在 ArrayList 中返回下一个和上一个对象
- python - csvjoin 错误:“强制转换为 Unicode:需要字符串或缓冲区,找到 LazyFile”
- haskell - 模块“Main”未导出 IO 操作“main”
- visual-studio-code - 我如何在 Windows 的 Visual Studio Code 中保存 Gitlab 用户名和密码?
- verilog - 在verilog中迭代数组的值
- python - PySpark - 无法连接来自同一个 RDD 的两个元素
- php - 您将如何解释 php 赋值语句?
- python - 我如何确定这个二维势场的准确性?