Actor Inferencing?

[ole (Ole Begemann)]

@newboadki

Do the task's context inheritance rules (link) exclusively refer to the lexical context? In other words, whenever that section mentions context, do they mean lexical context?

In his initial post, Chris mentioned that determining the execution context of async code is a purely lexical thing. Is this mentioned anywhere in the official documentation, an empirical observation, or derived from source code inspection?

I don't have a source in the official documentation, but here's a confirmation from @Douglas_Gregor in the Structured Concurrency review thread:

@Chris_Lattner3

The Context Inheritance section (and the later Actor context propagation section) says this about launching unstructured tasks from within an actor context:

• if executed within the scope of a specific actor function:
  • inherit the actor's execution context and run the task on its executor, rather than the global concurrent one,
  • the closure passed to Task {} becomes actor-isolated to that actor, allowing access to the actor-isolated state, including mutable properties and non-sendable values.

What does "specific actor function" mean in this case? Does that mean from within a method lexical defined on the actor type, or does this mean a function dynamically executing on an actor's executor?

It's the lexical context.