hash/maphash: add WriteComparable and Comparable #69166

qiulaidongfeng · 2024-08-30T11:25:14Z

Default, use hash function in the runtime package.
If the build tag is purego or raw memory cannot be hash directly,
use reflect get each field to hash separately.

Fixes #54670

gopherbot · 2024-08-30T11:31:09Z

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

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

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-30T11:47:11Z

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

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

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-30T12:09:25Z

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

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

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-30T12:16:51Z

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

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

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.

By default, runtime.memhash is used. When purego is used, reflect is used to generate the same []byte with the same value, and then hash the []byte. Fixes golang#54670 Change-Id: Ibd0538a7dfb3d831c5145970cac7c910692bca69

gopherbot · 2024-08-30T13:23:54Z

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

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

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-30T17:45:42Z

Message from Ingo Oeser:

Patch Set 5:

(7 comments)

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

Change-Id: Ic392ffab19c02982c8676f274932ba0d61cc54da

gopherbot · 2024-08-31T01:54:26Z

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

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

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.

Change-Id: I30d5017391a36d503844ff9bf8649a361e032ee9

gopherbot · 2024-09-01T08:04:43Z

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

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

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-01T11:31:20Z

Message from Ingo Oeser:

Patch Set 8:

(4 comments)

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

Change-Id: I930518778b9a29e5722d0fc149d54f8443605398

gopherbot · 2024-09-01T12:00:55Z

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

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

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-03T22:35:42Z

Message from Keith Randall:

Patch Set 11:

(9 comments)

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

Change-Id: I0460ecbbe8a7b564b72a36132a32b60d68aed7f4

gopherbot · 2024-09-04T13:00:03Z

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

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

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:16Z

Message from qiu laidongfeng2:

Patch Set 12: Commit-Queue+1

(19 comments)

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

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

Message from Go LUCI:

Patch Set 12:

Dry run: CV is trying the patch.

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

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

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

Message from qiu laidongfeng2:

Patch Set 12: -Commit-Queue

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

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

Message from Go LUCI:

Patch Set 12:

This CL has failed the run. Reason:

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

go on master (change 609761)

Build or test failure, click here for results.

To reproduce, try gomote repro 8737473116753544561.

Additional links for debugging:

Output for go tool dist test -json [shard 1]

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

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

Message from Go LUCI:

Patch Set 12: LUCI-TryBot-Result-1

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

Change-Id: If294c38f4b48106ea4e94d86c137eff3232598dd

gopherbot · 2024-09-07T08:03:05Z

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

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

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-07T08:09:42Z

Message from qiu laidongfeng2:

Patch Set 13: Commit-Queue+1

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

Change-Id: I969fbe5af7172c5a8fa052b3de9591177bdc7444

gopherbot · 2024-09-19T13:29:45Z

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

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

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-19T13:53:09Z

Message from qiu laidongfeng2:

Patch Set 16: Commit-Queue+1

(7 comments)

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

gopherbot · 2024-09-19T13:53:10Z

Message from Go LUCI:

Patch Set 16:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-09-19T13:37:56Z","revision":"44d94bdf1fee799f88c6b1fc0c3fb96718f84c56"}

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

gopherbot · 2024-09-19T14:08:27Z

Message from qiu laidongfeng2:

Patch Set 16: -Commit-Queue

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

gopherbot · 2024-09-19T14:08:27Z

Message from Go LUCI:

Patch Set 16:

This CL has passed the run

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

gopherbot · 2024-09-19T14:08:28Z

Message from Go LUCI:

Patch Set 16: LUCI-TryBot-Result+1

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

gopherbot · 2024-09-23T16:40:26Z

Message from Keith Randall:

Patch Set 16:

(2 comments)

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

Change-Id: Ib9092286e351cc7f488c414222478318a2ffbc76

Change-Id: Ieab593790872107f78483ffbe29f507e158b8825

Change-Id: Ie2804609c4ccff8102f8c118a39878c7f812cbed

gopherbot · 2024-09-24T13:25:07Z

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

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

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-24T14:02:43Z

Message from qiu laidongfeng2:

Patch Set 17: Commit-Queue+1

(2 comments)

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

gopherbot · 2024-09-24T14:02:43Z

Message from Go LUCI:

Patch Set 17:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-09-24T13:39:13Z","revision":"b52bca6e009e91035307177b5afb6b9399f5af69"}

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

gopherbot · 2024-09-24T14:24:52Z

Message from qiu laidongfeng2:

Patch Set 17: -Commit-Queue

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

gopherbot · 2024-09-24T14:24:53Z

Message from Go LUCI:

Patch Set 17:

This CL has passed the run

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

gopherbot · 2024-09-24T14:24:53Z

Message from Go LUCI:

Patch Set 17: LUCI-TryBot-Result+1

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

gopherbot · 2024-09-24T18:04:01Z

Message from Keith Randall:

Patch Set 17: Code-Review+2

(9 comments)

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

Change-Id: I6dec60bfec56e1c0b0bfa8ab2c65f305af426bfb

gopherbot · 2024-09-25T10:10:23Z

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

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

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-25T13:05:19Z

Message from qiu laidongfeng2:

Patch Set 19: Commit-Queue+1

(8 comments)

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

gopherbot · 2024-09-25T13:05:19Z

Message from Go LUCI:

Patch Set 19:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-09-25T12:55:18Z","revision":"0a3a360fafff811fce93f0407359f1a83b6c7ca7"}

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

gopherbot · 2024-09-25T13:31:28Z

Message from qiu laidongfeng2:

Patch Set 19: -Commit-Queue

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

gopherbot · 2024-09-25T13:31:29Z

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/609761.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2024-09-25T13:31:29Z

Message from Go LUCI:

Patch Set 19: LUCI-TryBot-Result+1

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

gopherbot · 2024-09-25T15:20:49Z

Message from Keith Randall:

Patch Set 19: Code-Review+1

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

gopherbot · 2024-09-26T14:54:52Z

Message from David Chase:

Patch Set 19: Code-Review+1

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

Default, use hash function in the runtime package. If the build tag is purego or raw memory cannot be hash directly, use reflect get each field to hash separately. Fixes #54670 Change-Id: Ic968864c9c3c51883967d4f6dc24432385c7dc79 GitHub-Last-Rev: 5ae8a28 GitHub-Pull-Request: #69166 Reviewed-on: https://go-review.googlesource.com/c/go/+/609761 Reviewed-by: Keith Randall <[email protected]> Reviewed-by: Keith Randall <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: David Chase <[email protected]>

gopherbot · 2024-10-02T16:03:46Z

This PR is being closed because golang.org/cl/609761 has been merged.

qiulaidongfeng force-pushed the 54670 branch from 96d4f44 to f4f4514 Compare August 30, 2024 11:27

qiulaidongfeng force-pushed the 54670 branch from f4f4514 to 7fad797 Compare August 30, 2024 11:42

qiulaidongfeng force-pushed the 54670 branch from 7fad797 to 9fc6340 Compare August 30, 2024 12:07

qiulaidongfeng force-pushed the 54670 branch from 9fc6340 to d4dcce9 Compare August 30, 2024 12:10

hash/maphash: add WriteComparable and Comparable

02df413

By default, runtime.memhash is used. When purego is used, reflect is used to generate the same []byte with the same value, and then hash the []byte. Fixes golang#54670 Change-Id: Ibd0538a7dfb3d831c5145970cac7c910692bca69

qiulaidongfeng force-pushed the 54670 branch from d4dcce9 to 02df413 Compare August 30, 2024 13:20

new

7668494

Change-Id: Ic392ffab19c02982c8676f274932ba0d61cc54da

fix bug

d498867

Change-Id: I30d5017391a36d503844ff9bf8649a361e032ee9

new

1ce6954

Change-Id: I930518778b9a29e5722d0fc149d54f8443605398

new

10f0778

Change-Id: I0460ecbbe8a7b564b72a36132a32b60d68aed7f4

new

6a2db95

Change-Id: If294c38f4b48106ea4e94d86c137eff3232598dd

new

f4ae01e

Change-Id: I969fbe5af7172c5a8fa052b3de9591177bdc7444

qiulaidongfeng added 3 commits September 24, 2024 21:09

new

6dccae2

Change-Id: Ib9092286e351cc7f488c414222478318a2ffbc76

new

84eeab9

Change-Id: Ieab593790872107f78483ffbe29f507e158b8825

new

d73a7a5

Change-Id: Ie2804609c4ccff8102f8c118a39878c7f812cbed

new

5ae8a28

Change-Id: I6dec60bfec56e1c0b0bfa8ab2c65f305af426bfb

gopherbot closed this Oct 2, 2024

hash/maphash: add WriteComparable and Comparable #69166

hash/maphash: add WriteComparable and Comparable #69166

Conversation

qiulaidongfeng commented Aug 30, 2024 • edited Loading

gopherbot commented Aug 30, 2024

gopherbot commented Aug 30, 2024

gopherbot commented Aug 30, 2024

gopherbot commented Aug 30, 2024

gopherbot commented Aug 30, 2024

gopherbot commented Aug 30, 2024

gopherbot commented Aug 31, 2024

gopherbot commented Sep 1, 2024

gopherbot commented Sep 1, 2024

gopherbot commented Sep 1, 2024

gopherbot commented Sep 3, 2024

gopherbot commented Sep 4, 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 19, 2024

gopherbot commented Sep 19, 2024

gopherbot commented Sep 19, 2024

gopherbot commented Sep 19, 2024

gopherbot commented Sep 19, 2024

gopherbot commented Sep 19, 2024

gopherbot commented Sep 23, 2024

gopherbot commented Sep 24, 2024

gopherbot commented Sep 24, 2024

gopherbot commented Sep 24, 2024

gopherbot commented Sep 24, 2024

gopherbot commented Sep 24, 2024

gopherbot commented Sep 24, 2024

gopherbot commented Sep 24, 2024

gopherbot commented Sep 25, 2024

gopherbot commented Sep 25, 2024

gopherbot commented Sep 25, 2024

gopherbot commented Sep 25, 2024

gopherbot commented Sep 25, 2024

gopherbot commented Sep 25, 2024

gopherbot commented Sep 25, 2024

gopherbot commented Sep 26, 2024

gopherbot commented Oct 2, 2024

qiulaidongfeng commented Aug 30, 2024 •

edited

Loading