On 4/9/26 20:11, Muneem via Std-Proposals wrote:
> My answer to Mr.Bjorn: I didn't say that you did have book keeping,
> infact that's the issue, like to copy a tuple elements in a variant and
> to make sure that you can't change the type of that variant to anything
> afterwards, you do need book keeping Information. Without a language
> level construct, you can't optimize such Information without breaking
> ABI's, just like how we needed flat maps, we need a language level
> construct.

std::variant already contains this bookkeeping, so no ABI changes are
needed.

Furthermore, the tuple visitor solution does not need such bookkeeping
at all.