: [go-nuts] How to find goroutines during debugging - aka goroutine labeling
On Wed, Mar 4, 2020 at 7:24 AM Florin Pățan <florinpa...@gmail.com> wrote:I think the current solution is a perfectly reasonable solution.As I explained in the article, you can have 0 performance impact when us
On Wed, Mar 4, 2020 at 7:24 AM Florin Pățan wrote:
> I think the current solution is a perfectly reasonable solution.
>
> As I explained in the article, you can have 0 performance impact when used
> in production environments, because you can disable this feature.
>
My experience is that a littl
I think the current solution is a perfectly reasonable solution.
As I explained in the article, you can have 0 performance impact when used
in production environments, because you can disable this feature.
And when used in debugging environments, this has a minimal performance
impact.
For more d
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.
