> debug.SetMemoryLimit will be useful (for me at least).
Me too! :) I need to read up more about it though. It seems to be a soft
limit, not a hard limit. We run in a container that has limited memory..
and anything we can do to make the GC aware of that limit would be nice..
-Eric
http://www.
debug.SetMemoryLimit will be useful (for me at least).
But a bit disappointed not to see a fix
for https://github.com/golang/go/issues/50603.
On Sunday, 12 June 2022 at 05:51:23 UTC+1 ben...@gmail.com wrote:
> I'm quite looking forward to the performance improvements we'll get for
> free (i.e.,
I'm quite looking forward to the performance improvements we'll get for
free (i.e., by just upgrading): sort will be faster, large switch blocks
will be faster due to now using jump tables (good for interpreter
opcode-dispatch loops), and regexp will be a little faster due to a
pointer-vs-value
On Sat, Jun 11, 2022 at 12:30 AM Amnon wrote:
>
> What are the biggest, and most exciting changes coming in 1.19?
The draft release notes are at https://tip.golang.org/doc/go1.19 .
1.18 was a big release with a lot of exciting changes. 1.19 is more
of a relaxed, catch your breath release. Pers
