How does scoped value inheritance work?

The term "inheritance" comes from thread-local variables, but scoped values work in a different way. First you bind a scoped value to a value, then you call a method that sees this binding. Now the question is: if this method creates new threads, can those threads see the scoped value binding you defined? The default answer is no.

There is one important exception: if this method creates a StructuredTaskScope, then the bindings are seen by the subtasks created by that scope. The reason is that none of these subtasks can escape the scope of the original method call, so the bindings cannot escape it either.

Scoped values are a great replacement for thread-local variables, and you should start using them now. They do not work in the same way, and because you control their life cycle when you bind them, they are much safer for your application.