7ded638ea3
Certain headers require `optional<T&>`, so it may be beneficial to split out `optional<T>` and `optional<T&>`. This can allow consumers to only bring in the `optional` flavour it needs.. - Parcel out the respective pieces into their own header. - Certain sources rely on transitive includes brought in by `<optional>`, so they're kept there for now, and only tests have been fixed. --------- Co-authored-by: Louis Dionne <ldionne.2@gmail.com> |
||
|---|---|---|
| .. | ||
| array.h | ||
| bit_reference.h | ||
| byte.h | ||
| complex.h | ||
| deque.h | ||
| format.h | ||
| fstream.h | ||
| functional.h | ||
| get.h | ||
| ios.h | ||
| istream.h | ||
| mdspan.h | ||
| memory.h | ||
| memory_resource.h | ||
| optional.h | ||
| ostream.h | ||
| pair.h | ||
| queue.h | ||
| span.h | ||
| sstream.h | ||
| stack.h | ||
| streambuf.h | ||
| string.h | ||
| string_view.h | ||
| subrange.h | ||
| tuple.h | ||
| variant.h | ||
| vector.h | ||