I understand the following is not the primary use-case,
but would work given the proposed facility:

On 5/25/26 07:12, Mital Ashok via Std-Proposals wrote:
> std::lazy<int> x = f(); // f is not called here
> return std::move(x)(); // f is called

The second line seems fine in isolation, but the first line appears
to change core language expression semantics simply via the presence
of a special library type used to specify the type of "x".

That's plain horrifying, both on an ergonomics level

  g(f()) // is f called here? maybe

and on an effort-for-specification level.

Jens