On Fri, 3 May 2024 at 13:05, Alexander Pavlov
wrote:
> Please note the https://pkg.go.dev/runtime/trace package, its
> documentation and following article (
> https://go.dev/blog/execution-traces-2024) provide good examples to start
> logging the GC.
>
Thank you! This is exactly what I needed!
Please note the https://pkg.go.dev/runtime/trace package, its documentation
and following article (https://go.dev/blog/execution-traces-2024) provide
good examples to start logging the GC.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsu
Sorry for the noise - looks like you meant when passing around objects by
this type, not just creating objects.
On Friday, May 3, 2024 at 11:02:37 AM UTC-6 Kevin Chowski wrote:
> If you are just unhappy about the A and A* while using a literal for C:
> note that if you are willing/able to write
If you are just unhappy about the A and A* while using a literal for C:
note that if you are willing/able to write a wrapper function instead of
using a literal, type inference works well today:
func NewC[E any, P Settable[E]](val []E) C[E, P] {
return C[E, P]{Val: val}
}
var c = NewC([]A{1, 2,
In golanglint_ci, there's a 'unused' linter, which will detect unused const
vars too.
Op vrijdag 3 mei 2024 om 00:18:02 UTC+2 schreef Ian Lance Taylor:
> On Thu, May 2, 2024 at 2:48 PM will@gmail.com
> wrote:
> >
> > Was this always the case? Is this a bug? Seems like it should be a
> com
