Looking at one of the bit less trivial samples included, the (C# Xpert) CancellationAndProgress, it seems nearly every method has the new async keyword.
Is this keyword only meant to highlight that the method has the new "asyncness" in the control flow? I'm thinking, if this is the case, wouldn't it be better to use the IDE graphical capabilities to make the dev aware that there's funky things going on if it really is that big deal. Or is the mainstream still coding in notepad so its important that you can easily from notepad tell this matter.
I think the IDE should provide capabilities similar to modern disassemblers, that is, insert graphical arrows to the left of the code that show what is going on incase there's something less obvious going on. Of course to improve scrolling performance those should only be visible when you hover to the outline strip which causes the outline to be highlighted. Or simply allow user to pick say a different background color for the particular line that has unusual flow / compiler magic.
Now if the keyword actually serves some purpose beyond enabling await to work in the method, then that's another matter but I didn't really get this from what I saw so far?
I just have a feeling I'm going to see async keyword glued to every method in my code and then if the purpose was to highlight something it's going to be pretty pointless.