C++ Logo


Advanced search

Re: [std-proposals] An efficient event-based coroutine solution

From: zys <dou1984_at_[hidden]>
Date: Sun, 3 Mar 2024 19:43:19 +0800 (CST)
     Hi, I have already completed the relevant paper, but I don’t know how to publish it. The paper is located at the following address:
     Please forgive any expression or grammar errors in the paper.

At 2023-10-03 07:05:15, "Gašper Ažman" <gasper.azman_at_[hidden]> wrote:

Dear ZYS,

I think you might want to know how the committee proposals work. If you want something to be accepted by the standard, you need to bring a paper, it's not common for someone else to write a paper on your behalf. People will help you with the procedural stuff, but they are unlikely to take the time to help with writing.

Once you have a paper that describes in detail how your design differs from p2300, the committee can have a discussion about it.


On Mon, Oct 2, 2023, 17:38 zys via Std-Proposals <std-proposals_at_[hidden]> wrote:


I have read "P2300R7 std::execution Published Proposal" before. But I think my implementation was more convenient, so I send the message。

The library main codes are all in this directory.:https://github.com/dou1984/coev/tree/main/src/coev

At 2023-09-29 21:23:48, "Jens Maurer" <jens.maurer_at_[hidden]> wrote:
>I'd suggest that you read https://isocpp.org/std/submit-a-proposal in detail.
>You've shown a few coroutine-based examples on that page, but it's unclear
>to me what the actual interface to the underlying functionality is.
>Which part does your library provide, and which part does the user have
>to provide? A Redis client library, for example, is not part of the
>C++ standard. Do you propose to make it so?
>Please also see P2300 for a more general execution framework
>(including interfacing with coroutines), and
>for integrating networking in that sender/receiver framework.
>What does your library offer that the combination of these two
>proposals does not provide?
>On 29/09/2023 15.09, zys via Std-Proposals wrote:
>> The c++20 coroutine is a high-performance coroutine solution, but it has not become popular, because there is no encapsulation that satisfies everyone.
>> The author provides a set of event-based encapsulation to separate from IO, network, and business code. Developers no longer need to implement coroutine encapsulation and can quickly convert existing asynchronous programs into coroutine programs.
>> The author's source code address is:https://github.com/dou1984/coev <https://github.com/dou1984/coev>

Std-Proposals mailing list

Received on 2024-03-03 11:43:32