async isn’t really part of your method signature

The async ‘modifier’ is just there to let the compiler know how to interpret your method contents.  It’s not a ‘real’ modifier like public, private, abstract, override, new, etc.

Over the weekend, saw a thread on StackOverflow where the person asking the question seemed to think that having a method use async/await affected the class hierarchy such that all subclasses had to use it too.  That’s not the case at all – the actual compiled results is a transformed version, of course, but more importantly, it’s still a ‘regular’ task.



VS update… with internal URL :)

Looks like RC (or whatever) bits are available with a product update:


The problem?  Clicking the Update button takes you to a url that doesn’t work outside of Microsoft’s internal network 🙂  Oops!


[EDIT] forgot to point out that I already have 11.0.50323 installed (the .1 build, even later than .0), so I’m guessing this is part of an initial hiccup in trying to push out a newer change.  Either that or some broken version checking logic that happened to kick in today. 🙂


Carmack being Carmack

He tweets:

I can send an IP packet to Europe faster than I can send a pixel to the screen. How f’d up is that?

Someone asks about it:

Transatlantic ping faster than sending a pixel to the screen?

Then it gets back to him, he creates an account (rounding error for ‘2 days’) and answers.  I’m not going to paste any of his answer here – go read it yourself!

It’s been a long time since I’ve had any kind of interaction with him, but this is Classic Carmack. 🙂

It’s also amusing to see his stats on the site after only answering a single question. 🙂