---
title: "Comment by OneLifeVibe on \"Ambient State in .NET 11 Async Code\" | Hashnode"
description: "The distinction between where a continuation runs and which ambient state travels with it is the part that sticks. The reminder that a logging scope or a tracin"
url: "https://hashnode.com/posts/ambient-state-in-net-11-async-code/6af8ab2d576765a570c65186/comment/6af8b5838547acf1fca4e949"
---

[Discussion](https://hashnode.com/posts/ambient-state-in-net-11-async-code/6af8ab2d576765a570c65186)

Comment [Ambient State in .NET 11 Async Code](https://hashnode.com/posts/ambient-state-in-net-11-async-code/6af8ab2d576765a570c65186)

[OneLifeVibe](https://hashnode.com/@onelifevibe)

[5h ago](https://hashnode.com/posts/ambient-state-in-net-11-async-code/6af8ab2d576765a570c65186/comment/6af8b5838547acf1fca4e949)

The distinction between where a continuation runs and which ambient state travels with it is the part that sticks. The reminder that a logging scope or a tracing activity can introduce AsyncLocal state through a dependency is especially useful, since searching a codebase for new AsyncLocal would miss it entirely. The six scenario benchmark also looks like a careful way to separate the cost of a stable value from the cost of changing it on every suspension.