Oops, thanks for that - seems the results from the first run of the example somehow got lost in the final version and I didn't notice.
The order of the output is dependent on when each call finished - they run in parallel, so it's not guaranteed that functions will end in the order they were invoked.
> In the brand new Visual Studio 2015 keyboard support has been dropped so that we could focus on delivering state-of-the-art handwriting recognition algorithms so that you can easily develop even the most complex applications with nothing more than a single finger or a stylus.
The order of the output is dependent on when each call finished - they run in parallel, so it's not guaranteed that functions will end in the order they were invoked.