Re: [go-nuts] Go 1.18 beta1: Embedding Type Parameter in struct definition is an error
On Tue, Dec 14, 2021 at 4:02 PM Kristoffer Semelka wrote: > > See above. This is mentioned in the appendix of the type parameters proposal > but doesn't work in this beta release. Was this marked out of scope for 1.18 > and if so where can I find a github issue for it? > > Minimal example: https://gotipplay.golang.org/p/YeMs-iAQwkr See https://golang.org/issue/49030. Ian -- 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 on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOyqgcUiZyatdfg26iYV9MPuXzUbfdvmk8WGC9WxpRwmTL4-WQ%40mail.gmail.com.
[go-nuts] Go 1.18 beta1: Embedding Type Parameter in struct definition is an error
See above. This is mentioned in the appendix of the type parameters proposal but doesn't work in this beta release. Was this marked out of scope for 1.18 and if so where can I find a github issue for it? Minimal example: https://gotipplay.golang.org/p/YeMs-iAQwkr -- 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 on the web visit https://groups.google.com/d/msgid/golang-nuts/CAEF0wegEcbF4sJHekZAySesyRnJQNuu399C4qDehAhDxfsSVuw%40mail.gmail.com.
[go-nuts] Go 1.18 Beta 1 is released
Hello gophers, We have just released go1.18beta1, a beta version of Go 1.18. It is cut from the master branch at the revision tagged go1.18beta1. Please try your production load tests and unit tests with the new version. Your help testing these pre-release versions is invaluable. Report any problems using the issue tracker: https://golang.org/issue/new If you have Go installed already, the easiest way to try go1.18beta1 is by using the go command: $ go install golang.org/dl/go1.18beta1@latest $ go1.18beta1 download You can download binary and source distributions from the usual place: https://golang.org/dl/#go1.18beta1 To find out what has changed in Go 1.18, read the draft release notes: https://tip.golang.org/doc/go1.18 Cheers, Cherry and Alex for the Go Team -- 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 on the web visit https://groups.google.com/d/msgid/golang-nuts/CAOW6Qth2JW-oVNiiWnoMPXnESigoLxgjbac-dYTmxh-W2YTPYA%40mail.gmail.com.
Re: [go-nuts] Why runtime force gc every 2 minutes?
Getting to Go: The Journey of Go's Garbage Collector Rick Hudson 12 July 2018 https://go.dev/blog/ismmkeynote Peter On Tuesday, December 14, 2021 at 9:05:09 AM UTC-5 peterGo wrote: > There is no right answer to your question. Optimiation is often a > balancing act between competing goals, for example, cpu vs menory, speed vs > memory safety, different workloads, avoiding worst cases, and so on. > > Here's a peek at the problem in 2018: > https://go.dev/blog/ismmkeynote.Since then, there have been other > refinements. In 2018,, a primary goal was to reduce gc latency. Once you > fix that, other issues come to the fore. > > Peter > > On Tuesday, December 14, 2021 at 4:14:14 AM UTC-5 kurnia...@gmail.com > wrote: > >> oh, maybe they just trying random configuration (1min, 5min, or something >> else) >> and 2min is the best result >> >> On Tuesday, December 14, 2021 at 4:13:05 PM UTC+7 Kurnia D Win wrote: >> >>> okay, thanks for the explanation, >>> suggesting me to change language to rust/c is not answering my curiosity >>> I ask it because I'm trying to learn the runtime, and the "why" behind >>> some decision that already made >>> for now, I will just follow it blindly, because the go developers >>> already made that decision >>> >>> thank you >>> >>> On Tuesday, December 14, 2021 at 3:27:18 PM UTC+7 Brian Candler wrote: >>> On Tuesday, 14 December 2021 at 03:28:26 UTC kurnia...@gmail.com wrote: > the problem with it, when you have a large live heap but with > efficient code (most of the hot code is zero alloc), the runtime will be > wasting CPU time every 2 minutes just to find out that there is no > garbage > to collect > Let's say it wastes, say, 10 milliseconds every 2 minutes - and it doesn't even stop the program for that time but runs GC in a separate thread. Is that a big deal, in order to give reasonable behaviour across a wide range of programs? If you need such fine low-level control, then maybe a different language like Rust (or even C) might be better for your application. > -- 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 on the web visit https://groups.google.com/d/msgid/golang-nuts/66383292-aace-47e4-99fb-50739aad0dabn%40googlegroups.com.
Re: [go-nuts] Why runtime force gc every 2 minutes?
There is no right answer to your question. Optimiation is often a balancing act between competing goals, for example, cpu vs menory, speed vs memory safety, different workloads, avoiding worst cases, and so on. Here's a peek at the problem in 2018: https://go.dev/blog/ismmkeynote.Since then, there have been other refinements. In 2018,, a primary goal was to reduce gc latency. Once you fix that, other issues come to the fore. Peter On Tuesday, December 14, 2021 at 4:14:14 AM UTC-5 kurnia...@gmail.com wrote: > oh, maybe they just trying random configuration (1min, 5min, or something > else) > and 2min is the best result > > On Tuesday, December 14, 2021 at 4:13:05 PM UTC+7 Kurnia D Win wrote: > >> okay, thanks for the explanation, >> suggesting me to change language to rust/c is not answering my curiosity >> I ask it because I'm trying to learn the runtime, and the "why" behind >> some decision that already made >> for now, I will just follow it blindly, because the go developers already >> made that decision >> >> thank you >> >> On Tuesday, December 14, 2021 at 3:27:18 PM UTC+7 Brian Candler wrote: >> >>> On Tuesday, 14 December 2021 at 03:28:26 UTC kurnia...@gmail.com wrote: >>> the problem with it, when you have a large live heap but with efficient code (most of the hot code is zero alloc), the runtime will be wasting CPU time every 2 minutes just to find out that there is no garbage to collect >>> >>> Let's say it wastes, say, 10 milliseconds every 2 minutes - and it >>> doesn't even stop the program for that time but runs GC in a separate >>> thread. Is that a big deal, in order to give reasonable behaviour across a >>> wide range of programs? >>> >>> If you need such fine low-level control, then maybe a different language >>> like Rust (or even C) might be better for your application. >>> -- 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 on the web visit https://groups.google.com/d/msgid/golang-nuts/90c4c799-bf1f-4850-9c42-8d346d80778bn%40googlegroups.com.
Re: [go-nuts] Why runtime force gc every 2 minutes?
oh, maybe they just trying random configuration (1min, 5min, or something else) and 2min is the best result On Tuesday, December 14, 2021 at 4:13:05 PM UTC+7 Kurnia D Win wrote: > okay, thanks for the explanation, > suggesting me to change language to rust/c is not answering my curiosity > I ask it because I'm trying to learn the runtime, and the "why" behind > some decision that already made > for now, I will just follow it blindly, because the go developers already > made that decision > > thank you > > On Tuesday, December 14, 2021 at 3:27:18 PM UTC+7 Brian Candler wrote: > >> On Tuesday, 14 December 2021 at 03:28:26 UTC kurnia...@gmail.com wrote: >> >>> the problem with it, when you have a large live heap but with efficient >>> code (most of the hot code is zero alloc), the runtime will be wasting CPU >>> time every 2 minutes just to find out that there is no garbage to collect >>> >> >> Let's say it wastes, say, 10 milliseconds every 2 minutes - and it >> doesn't even stop the program for that time but runs GC in a separate >> thread. Is that a big deal, in order to give reasonable behaviour across a >> wide range of programs? >> >> If you need such fine low-level control, then maybe a different language >> like Rust (or even C) might be better for your application. >> >>> -- 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 on the web visit https://groups.google.com/d/msgid/golang-nuts/d052caa3-d339-402f-8455-114087993eb7n%40googlegroups.com.
Re: [go-nuts] Why runtime force gc every 2 minutes?
okay, thanks for the explanation, suggesting me to change language to rust/c is not answering my curiosity I ask it because I'm trying to learn the runtime, and the "why" behind some decision that already made for now, I will just follow it blindly, because the go developers already made that decision thank you On Tuesday, December 14, 2021 at 3:27:18 PM UTC+7 Brian Candler wrote: > On Tuesday, 14 December 2021 at 03:28:26 UTC kurnia...@gmail.com wrote: > >> the problem with it, when you have a large live heap but with efficient >> code (most of the hot code is zero alloc), the runtime will be wasting CPU >> time every 2 minutes just to find out that there is no garbage to collect >> > > Let's say it wastes, say, 10 milliseconds every 2 minutes - and it doesn't > even stop the program for that time but runs GC in a separate thread. Is > that a big deal, in order to give reasonable behaviour across a wide range > of programs? > > If you need such fine low-level control, then maybe a different language > like Rust (or even C) might be better for your application. > >> -- 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 on the web visit https://groups.google.com/d/msgid/golang-nuts/d3e22652-749e-49da-912f-ac344bdb2f78n%40googlegroups.com.
Re: [go-nuts] Why runtime force gc every 2 minutes?
On Tuesday, 14 December 2021 at 03:28:26 UTC kurnia...@gmail.com wrote: > the problem with it, when you have a large live heap but with efficient > code (most of the hot code is zero alloc), the runtime will be wasting CPU > time every 2 minutes just to find out that there is no garbage to collect > Let's say it wastes, say, 10 milliseconds every 2 minutes - and it doesn't even stop the program for that time but runs GC in a separate thread. Is that a big deal, in order to give reasonable behaviour across a wide range of programs? If you need such fine low-level control, then maybe a different language like Rust (or even C) might be better for your application. > -- 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 on the web visit https://groups.google.com/d/msgid/golang-nuts/84107048-8822-4ecd-846f-70dc4ea64a02n%40googlegroups.com.
