Skip to content

cgo: zero cost cgo calling #51380

New issue
New issue
Closed
Closed
cgo: zero cost cgo calling#51380
Labels
FrozenDueToAgeProposal
Milestone
 
Proposal
@hiqsociety

Description

@hiqsociety
hiqsociety
opened on Feb 27, 2022

sorry for asking but is there a possibility for zero cost cgo calling in future?
140ns per call is too much.
rustlang has zero cost calling c / c++ now.
just wondering if that'll be the way in future.

Activity

hiqsociety
added
Proposal
on Feb 27, 2022
gopherbot
added this to the Proposal milestone on Feb 27, 2022
ALTree
changed the title [-]proposal: affected/package: cgo, zero cost cgo calling?[/-] [+]cgo: zero cost cgo calling[/+] on Feb 27, 2022
ALTree

ALTree commented on Feb 27, 2022

@ALTree
ALTree
on Feb 27, 2022 · edited by ALTree
Member

If it were easy to have zero cost cgo calls, it would've been done by now. It wasn't one of Go design goals to have effortless and performant C integration, and it's not easy for a language with a runtime like Go's. Anyway, this is #9704 and #19574, closing here as a dup.

ALTree
closed this as completedon Feb 27, 2022
golang
locked and limited conversation to collaborators on Feb 27, 2023
gopherbot
added
FrozenDueToAge
on Feb 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    FrozenDueToAgeProposal

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @ALTree@gopherbot@hiqsociety

        Issue actions
          cgo: zero cost cgo calling · Issue #51380 · golang/go