Subject: Re: [EXTERNAL] Macro for <coroutine>
From: Barry Revzin (barry.revzin_at_[hidden])
Date: 2020-01-14 19:45:44
I'm not sure, just thought I'd ask.
On Wed, Jan 15, 2020, 1:28 AM Gor Nishanov <gorn_at_[hidden]> wrote:
> Correct. You cannot define coroutine types, like a task or generator
> without including <coroutine> header.
> What would be the purpose of the __cpp_lib_coroutines?
> How do you envision it is going to be used?
> *From:* Barry Revzin <barry.revzin_at_[hidden]>
> *Sent:* Monday, January 13, 2020 9:07 PM
> *To:* sg10_at_[hidden] <sg10_at_[hidden]>
> *Cc:* lbaker_at_[hidden] <lbaker_at_[hidden]>; Gor Nishanov <gorn_at_[hidden]>
> *Subject:* [EXTERNAL] Macro for <coroutine>
> Hi SG10,
> We currently have the feature test macro __cpp_coroutines, but we have no
> macro for the library machinery in <coroutine>. I'm not super familiar with
> coroutines, but it seems like this works a lot like <=> and <compare> where
> you need the library bit to do anything?
> Should we then change the language macro to __cpp_impl_coroutines and
> introduce a new library macro __cpp_lib_coroutines, that users check for?
SG10 list run by firstname.lastname@example.org