Hey @liqingqing_1229, Welcome to openEuler Community.
All of the projects in openEuler Community are maintained by @openeuler-ci-bot.
That means the developers can comment below every pull request or issue to trigger Bot Commands.
Please follow instructions at https://gitee.com/openeuler/community/blob/master/en/sig-infrastructure/command.md to find the details.

Hi, @liqingqing, I'm Bin Gao, who inquired about this project through the mail before.
As you explained in the mail, we need to develop a language-level coroutine framework without hurting any current POSIX standards.

To do this, inspired by the existing solutions, I think we have the following aspects to discuss now.

1. stack design 2) scheduler. 3) how to communicate 4) what features to be supported in the prototype.

For the above questions, there are several designs and considerations in existing solutions, such as libgo, lthread, and libco. Learned from these libraries, I propose we answer the above question with these techniques.

1. shared virtual stack;
2. Cooperative and preemptive scheduling;
3. Shared value in the parent process;
4. this remains to be discussed, I think it's the first priority to just make it run under supporting the simplest features.

Our current task is to discuss and determine the architecture and design of this framework. It's important because we should consider the new features to make the future upgrades easy.

What're your opinions? Hope your suggestions.