Sergey Kopienko

May be I don’t understand what you mean, but I think it’s still possible for the users: * Instead of function overload whey should implement some full backend that they...

Should we think about ability to save previous behavior when the macros `TEST_LONG_RUN` is defined?

> > I think better if we will support all restrictions for these operators like in https://en.cppreference.com/w/cpp/utility/tuple : all these operators will be removed in C++20. > > @SergeyKopienko Can...

> > For me it's looks like we should implement all these operators only for C++17 version and implement `` operator for C++20. > > I'm wondering if it is...

@danhoeflinger It's not the result of you PR, but for `operator=(const tuple& other)` what about the case when `this == &other' ? I mean probably we should avoid self-assignment...

> > @danhoeflinger It's not the result of you PR, but for `operator=(const tuple& other)` what about the case when `this == &other' ? I mean probably we should avoid...

@danhoeflinger How do you think, should we support three-way comparison `` too (https://en.cppreference.com/w/cpp/language/operator_comparison)?

@julianmi, how do you think, should we introduce some type for the `union` ```C++ union __storage { _Tp __v; __storage() {} }; ``` ?

@AnuyaWelling2801, what do you think, will you apply this PR or I may close it?

I think alternative approach available too: https://github.com/oneapi-src/oneDPL/pull/1548 My assumption that better to include all required headers to have all required and used definition. Because lazy define initialization you correctly rewrite...