Subject: Re: [std-proposals] Feedback on implementing proposed std::error type
From: GaÅ¡per AÅ¾man (gasper.azman_at_[hidden])
Date: 2020-05-13 03:20:49
D2170R0 is yours :)
The next mailing is May 15th at 2pm UTC, so make sure you hit that. Sorry
for the rush.
On Wed, May 13, 2020 at 9:09 AM GaÅ¡per AÅ¾man <gasper.azman_at_[hidden]> wrote:
> Look at mpark/wg21 on GitHub.
> It's not the only way to format documents, but it helps. A paper has a
> particular structure you should follow, but since yours is not a proposal,
> you can skip the proposed wording.
> Once your paper is "in shape" I'll upload it to the tracker. I'll get you
> a paper number later today.
> On Tue, May 12, 2020, 15:35 Charles Salvia <charles.a.salvia_at_[hidden]>
>> Yes, thank you, that would be great. What is the process for publishing
>> in a mailing?
>> On Tue, May 12, 2020 at 2:41 AM GaÅ¡per AÅ¾man <gasper.azman_at_[hidden]>
>>> Do you need help publishing this in a mailing?
>>> On Tue, May 12, 2020, 06:00 Charles Salvia via Std-Proposals <
>>> std-proposals_at_[hidden]> wrote:
>>>> I've implemented std::error, meeting the requirements laid out in [
>>>> and based on this experience, have written up a paper outlining various
>>>> design decisions and concerns that came up during the implementation,
>>>> particularly with regard to how std::error might map to existing error
>>>> mechanisms (dynamic exceptions, std::error_code).
>>>> This is not a formal proposal right now. It is intended simply to
>>>> further discussion around the design, requirements and implementation
>>>> details of some future std::error specification.
>>>> Std-Proposals mailing list
STD-PROPOSALS list run by firstname.lastname@example.org
Standard Proposals Archives on Google Groups