[go-nuts] Re: go 1.21 tuned gc: what's it about?

I saw this post a while back and forgot to reply; sorry about that. It's about this issue but also a little bit about this issue . Both of those problems can be summarized as the GC pacing itself for the

[go-nuts] [ann] knoa (dealing with unstructured data)

I'm so happy to announce the very first release of *knoa * The goal of knoa is to provide *a handy way to deal with unstructured data* in #go #golang The below piece of code shows an example (You could find more examples here

Re: [go-nuts] What happened to sep in errorrs.join

On Mon, Aug 7, 2023 at 4:32 AM jal...@gmail.com wrote: > > In the errors.join proposal, the proposed api had the user specify how they > wanted the errors to be formatted together. But the actual implementation > omitted and only used new line. > > This is quite unfortunate if you are using

Re: [go-nuts] [testing] best practices for the test (client-server)

net/http/httptest is a great package, either to use if your server is http-based or to emulate if you’re testing other protocols. I’ve also found io.Pipe to frequently be useful for this kind of testing. I’d recommend reading through how net/http and x/net/http2 structures their tests. -eli

[go-nuts] [testing] best practices for the test (client-server)

Hi, Anyone have suggestion for writing test cases (best practices ) for client server communication. -- 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

[go-nuts] What happened to sep in errorrs.join

In the errors.join proposal , the proposed api had the user specify how they wanted the errors to be formatted together. But the actual implementation omitted and only used new line. This is quite unfortunate if you are using slog and want to log that

Re: [go-nuts] Bets approach for test helper packages within same project

Many thanks! Replying to myself as well: Build tags are still useful to separate away non unit tests that require some ad-hoc setup to be run. That way doing "go test ./..." on the project root works as expected. On the other hand, integration or end to end tests that require some setup or

Re: [go-nuts] Bets approach for test helper packages within same project

https://stackoverflow.com/a/54734212 On Monday, August 7, 2023 at 8:48:24 AM UTC+2 josvazg wrote: > Interesting! Thanks! > > I was assuming wrongly the module was the unit of compilation. > > If any package not imported by production code is not included, then that > also means that build tags

Re: [go-nuts] Bets approach for test helper packages within same project

Interesting! Thanks! I was assuming wrongly the module was the unit of compilation. If any package not imported by production code is not included, then that also means that build tags are not necessary for the integration and end to end test folders. Correct? Any pointers on where can I read