[cfe-dev] Is it the time to mark coroutine status as green in cxx_status page?

[Richard Smith via cfe-dev]

This feature is marked as partial, in part, because we don't know what's
missing. We implemented against a moving target (the C++ Coroutines TS and
evolving work towards the final standard feature), and there's no guarantee
we didn't miss changes along the way. So, the major piece of work we're
missing here is: someone needs to go through the sections on coroutines in
the C++ standard, and make sure that all the work listed there has been
implemented and is tested. Someone should also go through all the open bugs
on coroutines and see which ones are sufficiently important that we should
not claim conformance until we address them. That'll either result in a
todo list of the remaining items, or a conclusion that we are in fact done.

Once we're done, we'll need to update our feature test macro to match; then
we can mark it as done on the status page.

On Mon, 13 Dec 2021 at 18:55, chuanqi.xcq via cfe-dev <
cfe-dev at lists.llvm.org> wrote:

> Hi,
>
>    I noticed that the status of coroutine in cxx_status page is partial
> previously: https://clang.llvm.org/cxx_status.html.
>    This looks weird to me since coroutine is used broadly and stably in
> practice and I want to mark it as green. So I tried
> to move coroutine out of the experimental namespace before and implement
> the semantics of throwing unhandled_exception()
> suggested by Lewis.
>    So I sent https://reviews.llvm.org/D115692 to mark coroutine as done.
> I want to ask if there is any blocking issue to do this?
> I would love to try to fix any inconsistency.
>
> Thanks,
> Chuanqi
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20211214/056060db/attachment.html>