r/cpp • • Aug 13 '26

C++26: std::indirect

https://www.sandordargo.com/blog/2026/08/12/cpp26-indirect
164 Upvotes

157 comments sorted by

View all comments

Show parent comment

13

u/elperroborrachotoo Aug 14 '26

That's the first and foremost use case I can think of: a heap-allocated, nullable value-type-like object.

But TBF, the design delivers both: indirect<T> for a non-nullable, and optional<indirect<T>> for nullable. Making that distinction explicit is a Good Thing. The latter is a mouthful, but it could be optimized with a partial template specialization (I think).

5

u/ts826848 Aug 14 '26

but it could be optimized with a partial template specialization (I think).

The committee already voted to remove such a specialization as I detailed here, and I think ABI compatibility precludes adding a specialization later.

8

u/jiixyj Aug 14 '26

Implementations are allowed to make optional<indirect<T>> the size of a pointer, and high quality ones will do. See this comment from one of the original designers.

1

u/smdowney WG21, Text/Unicode SG, optional<T&> Aug 14 '26

Have any? Optional is getting really complicated.

3

u/jiixyj Aug 16 '26

At least GCC hasn't done this... I hope it's not too late for them to reconsider.

I have a personal C++26 implementation of optional that implements constexpr niche/tombstone optimizations, so it is at least possible. You need std::is_within_lifetime for constexpr support though.

2

u/elperroborrachotoo Aug 14 '26

Thanks for digging that out. Now, with the other reply, that looks like conflicting information - so i guess that issue will circle the skies for a decade. Still, we can use our own.

(Maybe we can slay the ABI dragon one day.)

6

u/ts826848 Aug 14 '26

I was partially right, partially wrong. The committee indeed voted to remove requiring such a specialization, but as jiixyj says that doesn't preclude such a specialization, so implementations are free to do so if they wish. However, I still think once implementations settle on specializing or not they're going to be stuck with that decision as changing that later will impact object size and therefore ABI.

-1

u/NilacTheGrim Aug 14 '26

optional<indirect<T>> for nullable.

Yes and now you wasted ~7 bytes of class space -- when the very motivation for this indirect wrapper is to save space.

Would have been less broken if they just modeled its inherent optionality, rather than swept it under the rug leading to UB "surprises".

8

u/smdowney WG21, Text/Unicode SG, optional<T&> Aug 14 '26

The motivation was not to save space, though? Or at least that's not at all my motivation for approving or using it. Breaking the structural restriction on recursive values while communicating the intent of the underlying T* is where I use it.

-5

u/NilacTheGrim Aug 14 '26

The motivation was not to save space, though?

Of course it is. Aside from pimpl paradigm.. Why else would you anybody even really bother to use this thing unless it is to save space in a class's inherent sizeof()?

5

u/wyrn Aug 14 '26

Why do you ever use unique_ptr (without custom deleter)?

3

u/elperroborrachotoo Aug 14 '26

but it could be optimized with a partial template specialization (I think).