Lewis Baker

Note that on modern versions of clang std::forward/move now get translated to intrinsics which shouldn’t have the same template instantiation overhead.

Can the `= default` definition be added later or should we target that for this change too?

I think it could be challenging to allow `= default` for an otherwise normal method. Maybe if it was named `operator co_await()` then it would be more palatable.

Have you tried applying the `[[nodiscard]]` attribute to the function or return-type? This attribute was intended for this sort of scenario. i.e. preventing the caller from accidentally ignoring/discarding the return-value....

I see your point. Another motivating example I came up with: ```c++ async_mutex mutex; task correct() { // co_await used, lock acquired correctly auto lock = co_await mutex.scoped_lock_async(); //... }...