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
Copy file name to clipboardExpand all lines: Sources/Instrumentation/Instrument.swift
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ import ServiceContextModule
19
19
/// The assocaited type, `Carrier`, is a service request such as an HTTP request,
20
20
/// that has string values that can be extracted to provide information for a tracing span.
21
21
///
22
-
/// Typically the library adopting instrumentation, would provide an implementation of this type, since it is aware of its carrier type.
22
+
/// Typically the library adopting instrumentation, would provide an implementation of this type, since it is aware of its carrier type.
23
23
/// Which then can be combined with instrumentation or tracing implementations, which are not aware of the concrete carrier, and only provide an ``Instrument`` (or `Tracer`) which makes use of injector/extractor to operate on carrier values.
24
24
publicprotocolExtractor:Sendable{
25
25
/// The carrier to extract values from.
@@ -37,7 +37,7 @@ public protocol Extractor: Sendable {
37
37
///
38
38
/// The associated type, `Carrier`, is often a client or outgoing request into which values are inserted for tracing spans.
39
39
40
-
/// Typically the library adopting instrumentation, would provide an implementation of this type, since it is aware of its carrier type.
40
+
/// Typically the library adopting instrumentation, would provide an implementation of this type, since it is aware of its carrier type.
41
41
/// Which then can be combined with instrumentation or tracing implementations, which are not aware of the concrete carrier, and only provide an ``Instrument`` (or `Tracer`) which makes use of injector/extractor to operate on carrier values.
0 commit comments