You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@Sajmani
The current trace package does not provide a way for the caller of trace.FromContext to know whether trace.Trace.Finish has been called on this Trace (usually by another goroutine) so that the caller may operate on a finished Trace.
The text was updated successfully, but these errors were encountered:
I think we should make calling trace's methods after Finish a no-op. This will require some refactoring since we recycle trace objects to reduce allocations.
adg
changed the title
issue with golang.org/x/net/trace
x/net/trace: no way to know whether Finish has been called
Oct 6, 2015
@Sajmani
The current trace package does not provide a way for the caller of trace.FromContext to know whether trace.Trace.Finish has been called on this Trace (usually by another goroutine) so that the caller may operate on a finished Trace.
The text was updated successfully, but these errors were encountered: