You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am still working through a test to ensure this functionality works. I am currently working through the reactor host setup to call the exported function.
Thanks, I have not seen this yet. I will read through it and follow up. Regardless, would you prefer I close this issue or leave it open until we can confirm the behavior outlined has been implemented/validated?
I am having similar issues with go 1.26, any updates on this ?
My current workaround is the same as the one mentioned above (passing all unsupported types to unsafe pointers) but this is really messy ...
Activity
ydnar commentedon Oct 1, 2024
golang/go#66984 fixes this
elewis787 commentedon Oct 1, 2024
Thanks, I have not seen this yet. I will read through it and follow up. Regardless, would you prefer I close this issue or leave it open until we can confirm the behavior outlined has been implemented/validated?
ydnar commentedon Oct 2, 2024
Sure, let's leave this open to track.
prep commentedon Oct 27, 2024
According to the proposal:
But when I generate from this:
It generates this:
Would it be fair to say this would be in error, even after the proposal is integrated?
ydnar commentedon Oct 27, 2024
A pointer to a string is a single i32, so it is valid as a return value.
ydnar commentedon Dec 8, 2024
Is this issue still valid?
therayquaza commentedon May 13, 2026
I am having similar issues with go 1.26, any updates on this ?
My current workaround is the same as the one mentioned above (passing all unsupported types to unsafe pointers) but this is really messy ...
elee1766 commentedon Jul 10, 2026
i think this issue is still valid yes. #66984 was closed but it only works for the wasm32 case.
would be there any interest in a pr for the unsafe pointer workaround?