This turned out to have faster performance and stability than libcurl. Thank you @bradfitz and the Go team.https://twitter.com/willie/status/880184435639017473 …
-
-
My first Go app ended up with a Go->C->Go call chain and I hit a bug in the runtime (that had been reported and unfixed for a year or so)
-
I ended up debugging and fixing it, but what I saw about the innards scared me off of using Go more, especially mixing with C. :(
End of conversation
New conversation -
-
-
The requirements were defined and documented a few releases back. There's also a runtime check for the rules. No as bad anymore.
-
Is there some kind of pinning mechanism for Go memory to avoid having to make copies?
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.