AsyncLocal never leaks and is safe for CallContext-like state
Even if it's typically used in a static field, the values never leak since they are bound to a transient ExecutionContext
Last updated
Even if it's typically used in a static field, the values never leak since they are bound to a transient ExecutionContext
Last updated
Sometime ago I wrote on , and one question mentioned that the values themselves might leak, which actually is not the case, as shown here, due to the "magic" that is AsyncLocal in combination with the :