Open CaseyCarter opened 5 years ago
This seemly damages throughput, since tuple
has a large number of constructors (and the number has increased in C++23) that might be not intentionally used as implementation details.
I suggest using a simplified version of tuple
as implementation details of both tuple
and other components.
Or, given that this is vNext anyways, use [[no_unique_address]]
to make your code simpler and faster to compile.
Once
tuple
"compresses" empty objects, we can likely simplify metaprogramming (for example, in the forwarding call wrappers https://github.com/microsoft/STL/pull/158#discussion_r336827719) by usingtuple
instead of_Compressed_pair
.vNext note: Resolving this issue will require breaking binary compatibility. We won't be able to accept pull requests for this issue until the vNext branch is available. See #169 for more information.