News for hackers. Stuff that matters.
Re:Optimizing Go string operations with practical examples by kiitos on Sunday December 03, 2023 @06:57AM (#38506431)
Be careful that you're not pooling buffers of wildly different sizes

Also this code has many many problems please never use it to encode JSON :)

Re:Optimizing Go string operations with practical examples by costco on Sunday December 03, 2023 @12:17PM (#38508701)
It's part of an API client I made for Resy so there are some guarantees on what characters will be in configID which is why I don't escape everything. I actually have a separate pool but I used bytebufferpool.Get instead of client.pool.Get when writing it here so the intent was clearer. But the code has gotten me Friday 7 PM reservations at Tatiana so it works though it's probably overkill because network latency is by far the biggest cost in terms of time. I probably should just have a JSON encoder write to the buffer.
Re:Optimizing Go string operations with practical examples by kiitos on Monday December 04, 2023 @10:16PM (#38526674)
If allocations aren't a major contributor to costs, then there's no reason to use a sync.Pool, is there?
Re:Optimizing Go string operations with practical examples by costco on Tuesday December 05, 2023 @11:36AM (#38533155)
It was fun to write and if more people start botting like I do it might eventually become useful. But yes it's premature if that's what you mean.