Author should explore further. Some directions from the mailing list:

1. A request for examples of usage of optional<T&>.
2. A request for detailed specification of the impact on current code and library. 
   (suggestions: uses of std::move(**this) change to *std::move(*this), also a question of return value T of all value_or functions is brought up)
3. Consider: making value_or variadic.
4. Related proposals:
   • http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p0798r4.html
   • http://open-std.org/JTC1/SC22/WG21/docs/papers/2014/n4120.pdf
   • http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p0927r2.pdf (might provide a similar lazy facility)
5. A request to focus on and add existing alternatives to the paper.
6. Please take under consideration a possible solution supported by Metaprogramming. (http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p2237r0.pdf)

Waiting for next revision.

Closing due to more than 1 year of inactivity. Please re-open if further work is expected.

Marc posted a draft to the reflector in February but I don't think he published it yet.