件人:
> "BiteThet"
> <
> pxl...@qq.com>;
> 发送时间: 2022年5月9日(星期一) 下午5:16
> 收件人: "dev"
> 主题: 回复： [DISCUSS] Update backend c++ standard to gnu20
>
>
>
> Maybe we can just
t;
>
>
> -- 原始邮件 --
> 发件人:
> "BiteThet"
> <
> pxl...@qq.com>;
> 发送时间: 2022年5月9日(星期一) 下午5:16
> 收件人: "dev"
> 主题: 回复： [DISCUSS] Update bac
Hi All,
The community recently added ci detection for clang build, which can
avoid build failures caused by some differences
between gcc and clang. I think now we can start talking again about whether we
should upgrade the C++ standard
from gnu++17 to gnu++20.
Over the past few months,
-- 原始邮件 --
>发件人:
> "dev"
> 发送时间: 2022年5月9日(星期一) 下午4:56
>收件人: "dev
Maybe we can just use the feature just both gcc and clang supported until we
decide to use gcc or clang.I think there won't be a lot of code involving new
features of the C++20 standard, so it's rare to meet compatibility problems.
-- --
??:
I checked the support of gcc[1] and clang[2] for the cxx20 standard, gcc
can partially support it, but the support of clang is poor. If it is
upgraded, how to ensure the compatibility of the code under gcc and clang
[1] https://gcc.gnu.org/projects/cxx-status.html#cxx20
[2] https://clang.llvm.org/
Hello everyone:
I want to update our c++ standard from gnu17 to gnu20, then we can use some new
feature such as `concept`,`coroutines`,`template lambda function`.
Currently our code doesn't need much modification to adapt to the c++20
standard, this is my pull-request
https://github.com/apache/i
