I do love #golang #cgo for interfacing to non-go (C) library code and system features. Much nicer than #jni and easy to wrap both C strings and structs, and doing so both ways. This made it simple to use #coventry ipc from apollo as well as to run the libeXosip2 stack under go.

I had been able to get an initial eXosip stack up on #golang with #cgo and it is proving ideal for writing simpler #sip clients and services quickly in #go.

Finally, with simd (hw acceleration), using sha256-simd in go and sha2 in rust through cgo (static library) is roughly equivalent, rust is slightly worse because of the overhead of cgo.

#golang #RustLang #cgo

Fun experiment today with #RustLang and #Golang where I checked if it would be faster to compute a large number of sha256 hashes directly in go or by using #rust one of two ways: as a statically linked library with #cgo and as a separate process using unix-domain sockets for IPC. Turns out go is always faster, with my setup around 40%. I benchmarked pretty much all the crates I could find for it but go's "crypto/sha256" is damn fast.

Salve ragazzi, c'è qualcuno che lavora con #golang e #cgo? Ho scritto un package che si interfaccia con una DLL che ho scritto e vorrei sapere se nella distribuzione del package .go devo includere i file header, linker (il file .a per chi usa gcc) e il file .def della dll.

@vazub I generally don't have problems with #golang projects, unless they have to do with #sqlite. Though there has been a pure Go driver for quite a while, many packages still use the #cgo one, which is a sure-fire way to break all of my builds.

#cgo is where the #golang dream goes to die.

#cgo is where the #golang dream goes to die.

CVE-2020-28367 (go) - Code injection in the go command with cgo before Go 1.14.12 and Go 1.15.5 allows arbitrary code execution at build time via malicious gcc flags specified via a #cgo directive. #nist

https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-28367

Hey #gopher|s,

I need your help:

I'm currently working on a project heavily involving cgo. Now I have a go function that gets a pointer and a length from a c lib. It needs to write byte data with the specific length into the c memory where the pointer points (yeah this is kind of a buffer you could say). How could I do this?

#golang #cgo