runtime/cgo: add support for `any` param and return type #76325

alexandre-daubois · 2025-11-17T09:50:02Z

When using any as param or return type of an exported function, we currently have the error unrecognized Go type any. any is an alias of interface{} which is already supported.

This would avoid such change: php/frankenphp#1976

gopherbot · 2025-11-17T10:02:30Z

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

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

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 · 2025-11-17T10:11:07Z

Message from Gopher Robot:

Patch Set 1:

(1 comment)

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

gopherbot · 2025-11-17T10:11:08Z

Message from Gopher Robot:

Patch Set 1:

Congratulations on opening your first change. Thank you for your contribution!

Next steps:
A maintainer will review your change and provide feedback. See
https://go.dev/doc/contribute#review for more info and tips to get your
patch through code review.

Most changes in the Go project go through a few rounds of revision. This can be
surprising to people new to the project. The careful, iterative review process
is our way of helping mentor contributors and ensuring that their contributions
have a lasting impact.

During May-July and Nov-Jan the Go project is in a code freeze, during which
little code gets reviewed or merged. If a reviewer responds with a comment like
R=go1.11 or adds a tag like "wait-release", it means that this CL will be
reviewed as part of the next development cycle. See https://go.dev/s/release
for more details.

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

gopherbot · 2025-11-17T18:51:21Z

Message from Ian Lance Taylor:

Patch Set 1:

(1 comment)

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

gopherbot · 2025-11-18T09:37:03Z

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

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

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 · 2025-11-18T09:45:47Z

Message from Alexandre Daubois:

Patch Set 1:

(2 comments)

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

gopherbot · 2025-11-18T09:45:48Z

Message from Alexandre Daubois:

Patch Set 2:

(1 comment)

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

gopherbot · 2025-11-18T23:14:23Z

Message from Ian Lance Taylor:

Patch Set 2: Commit-Queue+1

(1 comment)

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

gopherbot · 2025-11-18T23:22:31Z

Message from Go LUCI:

Patch Set 2:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-11-18T23:06:17Z","revision":"2e5361563fba38904fc599d16d712cb3583fa085"}

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

gopherbot · 2025-11-18T23:30:33Z

Message from Ian Lance Taylor:

Patch Set 2: -Commit-Queue

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

gopherbot · 2025-11-18T23:30:33Z

Message from Go LUCI:

Patch Set 2:

This CL has passed the run

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

gopherbot · 2025-11-18T23:30:34Z

Message from Go LUCI:

Patch Set 2: LUCI-TryBot-Result+1

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

gopherbot · 2025-11-18T23:38:35Z

Message from Sean Liao:

Patch Set 2:

(1 comment)

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

gopherbot · 2025-11-19T08:46:45Z

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

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

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.

When using `any` as param or return type of an exported function, we currently have the error `unrecognized Go type any`. `any` is an alias of `interface{}` which is already supported. This would avoid such change: php/frankenphp#1976 Fixes golang#76340

gopherbot · 2025-11-19T08:55:28Z

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

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

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 · 2025-11-19T09:15:01Z

Message from Alexandre Daubois:

Patch Set 4:

(3 comments)

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

gopherbot · 2025-11-19T21:19:08Z

Message from Keith Randall:

Patch Set 4:

(1 comment)

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

alexandre-daubois mentioned this pull request Nov 17, 2025

fix(extgen): replace any by interface{} in the generated go file when dealing with handles php/frankenphp#1976

Merged

austinderek mentioned this pull request Nov 17, 2025

runtime/cgo: add support for any param and return type PullRequestInc/go#184

Open

alexandre-daubois force-pushed the cgo-any branch from 73c34cf to ba1f629 Compare November 18, 2025 09:35

alexandre-daubois force-pushed the cgo-any branch from ba1f629 to 5c90847 Compare November 19, 2025 08:45

alexandre-daubois force-pushed the cgo-any branch from 5c90847 to 8e4e149 Compare November 19, 2025 08:48

runtime/cgo: add support for any param and return type #76325

Are you sure you want to change the base?

runtime/cgo: add support for any param and return type #76325

Conversation

alexandre-daubois commented Nov 17, 2025

Uh oh!

gopherbot commented Nov 17, 2025

Uh oh!

gopherbot commented Nov 17, 2025

Uh oh!

gopherbot commented Nov 17, 2025

Uh oh!

gopherbot commented Nov 17, 2025

Uh oh!

gopherbot commented Nov 18, 2025

Uh oh!

gopherbot commented Nov 18, 2025

Uh oh!

gopherbot commented Nov 18, 2025

Uh oh!

gopherbot commented Nov 18, 2025

Uh oh!

gopherbot commented Nov 18, 2025

Uh oh!

gopherbot commented Nov 18, 2025

Uh oh!

gopherbot commented Nov 18, 2025

Uh oh!

gopherbot commented Nov 18, 2025

Uh oh!

gopherbot commented Nov 18, 2025

Uh oh!

gopherbot commented Nov 19, 2025

Uh oh!

gopherbot commented Nov 19, 2025

Uh oh!

gopherbot commented Nov 19, 2025

Uh oh!

gopherbot commented Nov 19, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

runtime/cgo: add support for `any` param and return type #76325

runtime/cgo: add support for `any` param and return type #76325