It looks like P2549R0's title is "std::unexpected<E> should have
error() as member accessor" -- on the original question, though, I
would vote +1, since I would want new introductions of std::print into
existing code to interoperate correctly.
mfh

On Tue, May 10, 2022 at 9:11 AM Inbal Levi via Lib-Ext
<lib-ext_at_[hidden]> wrote:
>
> (LEWG was accidentally dropped from the thread, re-adding)
> Please notice this is targeting C++23
>
> +1
>
> The reason is that I don't want to introduce a somewhat unexpected behaviour in the new facility
>
> On Mon, 2 May 2022 at 13:17, Corentin <corentin.jabot_at_[hidden]> wrote:
>>
>> I'd like to see a few +1 on here, before we can move this paper to electronic polling.
>>
>> Thanks
>>
>> On Thu, Apr 28, 2022, 06:16 Jeff Garland <jeff_at_[hidden]> wrote:
>>>
>>>
>>>
>>> > On Apr 27, 2022, at 2:30 PM, Tomasz Kamiński via Lib-Ext <lib-ext_at_[hidden]> wrote:
>>> >
>>> > +1
>>>
>>> +1
>>>
> _______________________________________________
> Lib-Ext mailing list
> Lib-Ext_at_[hidden]
> Subscription: https://lists.isocpp.org/mailman/listinfo.cgi/lib-ext
> Link to this post: http://lists.isocpp.org/lib-ext/2022/05/23169.php