This is awesome and sad. The marketplace is now steering Go - which was bound to happen. You can't ignore the needs of the marketplace and expect it to standstill. This is a clear feature that the Go team (and community) should of taken more seriously and a better solution would of been delivered. But at least it's solved (at the expense of performance).
-----Original Message-----
From: Florin Pățan
Sent: Mar 3, 2020 9:11 AM
To: golang-nuts
Subject: [go-nuts] How to find goroutines during debugging - aka goroutine labeling--Hello gophers,There have been a number of posts in the past discussing how to handle large number of goroutines in applications when it comes to debugging them.Since Delve, the Go debugger, and GoLand, the Go IDE from JetBrains, recently got the ability to handle these, I thought I'd share this quick post on how to use this feature and make your life easier.You can find it here: https://blog.jetbrains.com/go/2020/03/03/how-to-find-goroutines-during-debugging/Looking forward for your thoughts on this.
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/47087123-a14a-4139-af84-7208a05a5ca1%40googlegroups.com.
--
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/427390762.3243.1583275086536%40wamui-pluto.atl.sa.earthlink.net.