hi Jason, On Thu Oct 30, 2025 at 08:31 CET, Jason E. Aten wrote: > Hi Sebastien, > > Given that Cargo is so much less secure than Go (no > equivalent of a module proxy), it might > be safer to let the Rust project be the "lead" or "top level" > project, and have the Rust build script; these > > https://doc.rust-lang.org/stable/cargo/reference/build-scripts.html > > pull in any Go dependencies.
I considered this, mainly to have something like PyO3 but for Go (taking care of the minutiae of exchanging slices and stuff, generating header files for Cgo). but cbindgen does most of that already. however, using Rust's infrastructure as the driver won't allow for the resulting Go package to be easily "go get"-able nor easily import-able from client packages. (unless I've missed something) and that's the main issue/goal of this email plea. Perhaps the title of this discussion should be rewritten as: "how to wrap large libraries via Cgo and make these packages play nice with the pure-Go ecosystem ?" -s -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/DDVQ6VY6HQBF.3ADGCHCIXRJ2G%40cern.ch.
