My proposal is a fire-and-forget strategy, and that is distinct from async let. However, the original proposal as well as the current documentation for async let does describe its behavior as I mentioned. The core part of async let that I was referencing as similar was specifically the asynchronous background execution of the captured operation. The difference is that operations using this hypothetical keyword would never be awaited (explicitly or implicitly) from the current context.
1 Like