Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.

3recommend
0warn against
Dec 12, 2025first mention
May 17, 2026latest mention
Nov 25 – Oct 26
Used forcall c from gocalling c from go without cgocalling native functions from godynamic loading shared objects in gocalling c libraries from go

Why people recommend it

“You can just embed the C library into the binary of the Go app call it directly in Go.”

“If you want to avoid Cgo, you can use https://github.com/ebitengine/purego”

Show 2 more

“The purego lib generalizes this idea. I haven't got round to trying this yet but it looks very promising.”

“you can use https://github.com/ebitengine/purego to generate the bindings”

Caveats and dissent

No one in these comments warned against it.

All comments 6

“Initial release wraps the API using purego”

“You can just embed the C library into the binary of the Go app call it directly in Go.”

“purego supports 8 GOARCHes and 20+ OS×ARCH combinations”

“If you want to avoid Cgo, you can use https://github.com/ebitengine/purego”

“The purego lib generalizes this idea. I haven't got round to trying this yet but it looks very promising.”

“you can use https://github.com/ebitengine/purego to generate the bindings”

Threads where it came up

Data: purego.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.

Keyboard shortcuts
j / kNext / previous item
o or EnterOpen selected item
/Search
g hHome
g tTop
g rRising
g cCategories
tToggle dark mode
?This help