[swift-evolution] New async keyword usage

[Jonathan Hull]

Why wouldn’t b wait for a in this example?  If it is using futures, those aren’t available in the current proposal.

> On Aug 25, 2017, at 3:02 PM, Florent Vilmart <florent at flovilmart.com> wrote:
> 
> Probably with:
> 
> let a = longCalculationA() 
> let b = longCalculationB() //b doesn’t wait for a to complete before starting
> let c = longCalculationC() //c doesn’t wait for a or b
> let (aResult, bResult, cResult) = await Future.collect(a, b, c) //waits until a, b, and c are all available
> 
> On 25 août 2017 17:48 -0400, wrote:
>> 
>> let a = async longCalculationA()
>> let b = async longCalculationB() //b doesn’t wait for a to complete before starting
>> let c = async longCalculationC() //c doesn’t wait for a or b
>> let result = await combineCalculations(a: a, b: b, c: c) //waits until a, b, and c are all available

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170825/de42bd83/attachment.html>