Martisch

some hardware effects I have come across: - [ ] loop optimized (or not) by Loop Stream Detector instruction queue replay - [ ] loop/branch misalignment - [ ] macro-fusable...

I also have seen a `detach` package before with a function `FromContext` that takes a parent context and creates a new context without propagation of the cancelation deadline and returns...

A possible solution to showing high level usage of different query paths can be achieved by setting profiling labels on the goroutine: https://golang.org/src/runtime/pprof/runtime.go?s=1362:1432#L26 And doing background profiling on the job:...

I do not like the stutter of _. Maybe func could be replaced by a keyword that infers the type parameters: ```s.Write(ctx, λ(p) { return p.SetData([]byte("Hello, ")) })```

One problem I see that narrows the scope where this is applicable is that `ids[i] = arr[0]` might never be reached depending on what `logger.Info` does and that might be...

go tool pprof imports https://github.com/google/pprof These samples in proto profile format generally allow labels: [Proto definition](https://github.com/google/pprof/blob/dcb5510988eb33b1f6ce96939b7ad97ed95db32f/proto/profile.proto#L117). The parsing happens with proto unmarshalling: [link](https://github.com/google/pprof/blob/d6d2dc122c202476d1eacc56b587de6a95d4fae5/profile/proto.go) The sample struct in go then contains...