I don’t think either suggestion was unhelpful. My first thought was the library was broken as well, as Ian provided some evidence of. And not using CGO should almost always be your first choice when there are Go only solutions available. Too many things to get right in a highly concurrent system when CGO is involved - and I suspect greater than 90% of all runtime bugs in Go programs.
> On Dec 2, 2024, at 4:43 PM, Jason E. Aten <j.e.a...@gmail.com> wrote: > > Sorry. I've deleted those unhelpful suggestions. > > > -- > 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 golang-nuts+unsubscr...@googlegroups.com > <mailto:golang-nuts+unsubscr...@googlegroups.com>. > To view this discussion visit > https://groups.google.com/d/msgid/golang-nuts/455959a3-4ddf-42b9-9d06-4d651effd7e2n%40googlegroups.com > > <https://groups.google.com/d/msgid/golang-nuts/455959a3-4ddf-42b9-9d06-4d651effd7e2n%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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 golang-nuts+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/FA1E7D0C-DD12-4FA1-9BCB-DF030FC22974%40ix.netcom.com.
