runtime/mainthread: new package #69185

qiulaidongfeng · 2024-08-31T08:48:07Z

New function Do,Yield,Waiting
coordinate the main thread using three channal and sync.Once.

Fixes #64777

gopherbot · 2024-08-31T08:58:44Z

This PR (HEAD: 3b4d81d) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/609977.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-08-31T09:05:59Z

This PR (HEAD: 68ed7f1) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/609977.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-08-31T09:13:16Z

This PR (HEAD: 081ed1c) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/609977.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-08-31T13:51:58Z

This PR (HEAD: 274de86) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/609977.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-09-02T07:23:15Z

This PR (HEAD: 849e8a2) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/609977.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-09-03T14:18:43Z

This PR (HEAD: 31d2cc3) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/609977.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-09-05T12:53:29Z

This PR (HEAD: ea2e55f) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/609977.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-09-05T13:01:22Z

This PR (HEAD: 4dcc3cd) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/609977.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-09-06T05:17:04Z

This PR (HEAD: 6f69909) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/609977.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-09-06T06:15:04Z

This PR (HEAD: ada39ca) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/609977.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-09-07T07:22:18Z

Message from qiu laidongfeng2:

Patch Set 11: Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-07T07:28:48Z

Message from Go LUCI:

Patch Set 11:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-09-07T07:15:27Z","revision":"abd11a8666d05a99638ee5db8d833a0d154f455f"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-07T07:35:20Z

Message from qiu laidongfeng2:

Patch Set 11: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-07T07:35:21Z

Message from Go LUCI:

Patch Set 11:

This CL has failed the run. Reason:

Tryjob golang/try/gotip-linux-arm64 has failed with summary (view all results):

go on master (change 609977)

Build or test failure, click here for results.

To reproduce, try gomote repro 8737473102036308881.

Additional links for debugging:

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-07T07:35:21Z

Message from Go LUCI:

Patch Set 11: LUCI-TryBot-Result-1

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

DO NOT SUBMIT -- f call Do now not panic New Function Do,Yield,Waiting coordinate the main thread using two channal. Fixes golang#64777 Change-Id: Ib15a03c0efc6db83a7819acc865a896752797341

Change-Id: I6727b54b5374fdf49665925e80dcd1b8813fafc3

Change-Id: I887451529534844ffb2ac85fd4b1b897176a062e

Change-Id: I140f20fa2c1cb092801ff13f8b954e32b02577d0

Change-Id: I43f2dbd678860136f67e7f5178c122456514ef0c

Change-Id: Ibfe3f33e832d84b1e02cba0e0eff379e8bc83c23

Change-Id: Ib2674eca814b56db5408009cefc1f8544f5a717c

Change-Id: I2b917610a120944e66f3b28bd8e394fa9fe54e50

Change-Id: Ifa789ebd6fed1e6e9afaf8b363d739547f9e8280

Change-Id: Ia43c1f0b7e846950326f4666f446fed6ef032f1e

Change-Id: I160b8f630d0a371908998cd74f0d38f1f4fd5b7e

Change-Id: I403b4ef8f3dd3e9d503c994c6a18b5cfb3a782c5

gopherbot · 2024-09-07T07:48:56Z

This PR (HEAD: aa61e08) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/609977.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-09-07T07:56:05Z

This PR (HEAD: 23287db) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/609977.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-09-07T11:11:34Z

Message from qiu laidongfeng2:

Patch Set 19: Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-07T11:18:35Z

Message from Go LUCI:

Patch Set 19:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-09-07T11:05:13Z","revision":"06eec05a913f773692ec9dd750ede096758f2f02"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-07T11:32:00Z

Message from qiu laidongfeng2:

Patch Set 19: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-07T11:32:00Z

Message from Go LUCI:

Patch Set 19:

This CL has passed the run

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-07T11:32:01Z

Message from Go LUCI:

Patch Set 19: LUCI-TryBot-Result+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-23T13:58:05Z

Message from qiu laidongfeng2:

Patch Set 19:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-24T08:35:16Z

Message from Elias Naur:

Patch Set 19:

(2 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-24T12:38:14Z

Message from qiu laidongfeng2:

Patch Set 19:

(2 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

Change-Id: I5905199f54000bb9fd64478c4110697b48e189ff

gopherbot · 2024-09-26T13:19:43Z

This PR (HEAD: e8d48cd) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/609977.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-09-26T14:06:18Z

Message from qiu laidongfeng2:

Patch Set 20: Commit-Queue+1

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-26T14:06:18Z

Message from Go LUCI:

Patch Set 20:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-09-26T13:59:19Z","revision":"4f4f0f553e74f628afd65462562bceee9492c434"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-26T14:30:17Z

Message from qiu laidongfeng2:

Patch Set 20: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-26T14:30:18Z

Message from Go LUCI:

Patch Set 20:

This CL has passed the run

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-26T14:30:18Z

Message from Go LUCI:

Patch Set 20: LUCI-TryBot-Result+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-30T19:22:55Z

Message from Elias Naur:

Patch Set 20:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-01T03:22:03Z

Message from qiu laidongfeng2:

Patch Set 20:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-02T07:44:03Z

Message from Elias Naur:

Patch Set 20:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-02T08:12:02Z

Message from qiu laidongfeng2:

Patch Set 20:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-06T17:10:57Z

Message from Elias Naur:

Patch Set 20:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-06T22:25:34Z

Message from qiu laidongfeng2:

Patch Set 20:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-10T11:34:57Z

Message from Elias Naur:

Patch Set 20:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-10T13:11:43Z

Message from qiu laidongfeng2:

Patch Set 20:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-14T19:10:44Z

Message from Elias Naur:

Patch Set 20:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-15T06:53:29Z

Message from qiu laidongfeng2:

Patch Set 20:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-16T19:50:29Z

Message from Elias Naur:

Patch Set 20:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-17T17:25:29Z

Message from qiu laidongfeng2:

Patch Set 20:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-18T08:40:50Z

Message from Elias Naur:

Patch Set 20:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-18T16:37:20Z

Message from qiu laidongfeng2:

Patch Set 20:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-10-21T07:39:39Z

Message from Elias Naur:

Patch Set 20:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/609977.
After addressing review feedback, remember to publish your drafts!

qiulaidongfeng added 12 commits September 7, 2024 15:48

runtime/mainthread: new package

6ca690d

DO NOT SUBMIT -- f call Do now not panic New Function Do,Yield,Waiting coordinate the main thread using two channal. Fixes golang#64777 Change-Id: Ib15a03c0efc6db83a7819acc865a896752797341

new

6c1714b

Change-Id: I6727b54b5374fdf49665925e80dcd1b8813fafc3

new

ff3e23d

Change-Id: I887451529534844ffb2ac85fd4b1b897176a062e

new

1058d8b

Change-Id: I140f20fa2c1cb092801ff13f8b954e32b02577d0

new

62c03d2

Change-Id: I43f2dbd678860136f67e7f5178c122456514ef0c

new

2bb2891

Change-Id: Ibfe3f33e832d84b1e02cba0e0eff379e8bc83c23

If f calls Do, panic

72b96a7

Change-Id: Ib2674eca814b56db5408009cefc1f8544f5a717c

new

2b65129

Change-Id: I2b917610a120944e66f3b28bd8e394fa9fe54e50

new

d608d98

Change-Id: Ifa789ebd6fed1e6e9afaf8b363d739547f9e8280

fix race in m0func not send and Yield in <-m0func

5f84bb1

Change-Id: Ia43c1f0b7e846950326f4666f446fed6ef032f1e

new

914ade4

Change-Id: I160b8f630d0a371908998cd74f0d38f1f4fd5b7e

new

23287db

Change-Id: I403b4ef8f3dd3e9d503c994c6a18b5cfb3a782c5

qiulaidongfeng force-pushed the 64777 branch from aa61e08 to 23287db Compare September 7, 2024 07:48

new

e8d48cd

Change-Id: I5905199f54000bb9fd64478c4110697b48e189ff

runtime/mainthread: new package #69185

Are you sure you want to change the base?

runtime/mainthread: new package #69185

Conversation

qiulaidongfeng commented Aug 31, 2024 • edited Loading

gopherbot commented Aug 31, 2024

gopherbot commented Aug 31, 2024

gopherbot commented Aug 31, 2024

gopherbot commented Aug 31, 2024

gopherbot commented Sep 2, 2024

gopherbot commented Sep 3, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 5, 2024

gopherbot commented Sep 6, 2024

gopherbot commented Sep 6, 2024

gopherbot commented Sep 7, 2024

gopherbot commented Sep 7, 2024

gopherbot commented Sep 7, 2024

gopherbot commented Sep 7, 2024

gopherbot commented Sep 7, 2024

gopherbot commented Sep 7, 2024

gopherbot commented Sep 7, 2024

gopherbot commented Sep 7, 2024

gopherbot commented Sep 7, 2024

gopherbot commented Sep 7, 2024

gopherbot commented Sep 7, 2024

gopherbot commented Sep 7, 2024

gopherbot commented Sep 23, 2024

gopherbot commented Sep 24, 2024

gopherbot commented Sep 24, 2024

gopherbot commented Sep 26, 2024

gopherbot commented Sep 26, 2024

gopherbot commented Sep 26, 2024

gopherbot commented Sep 26, 2024

gopherbot commented Sep 26, 2024

gopherbot commented Sep 26, 2024

gopherbot commented Sep 30, 2024

gopherbot commented Oct 1, 2024

gopherbot commented Oct 2, 2024

gopherbot commented Oct 2, 2024

gopherbot commented Oct 6, 2024

gopherbot commented Oct 6, 2024

gopherbot commented Oct 10, 2024

gopherbot commented Oct 10, 2024

gopherbot commented Oct 14, 2024

gopherbot commented Oct 15, 2024

gopherbot commented Oct 16, 2024

gopherbot commented Oct 17, 2024

gopherbot commented Oct 18, 2024

gopherbot commented Oct 18, 2024

gopherbot commented Oct 21, 2024

qiulaidongfeng commented Aug 31, 2024 •

edited

Loading