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.

Results:

image

VS update… with internal URL :)

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

image

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

image

[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. :)

image

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. :)

image

ran through the Ruby Koans

I did most of the Ruby Koans last night and finished it up today.

image

Most of it felt ‘right’ (at least with my history in perl/python/etc) although a few of them seemed a bit odd (at least in 1.9.3 behavior).

The ones that stuck out as odd (at least, IMHO) were:

array slicing with the first index that is invalid

This is a test that passes:

I’m assuming there’s a particular use case (and/or legacy behavior) behind that, but it seemed odd to me.

‘here’ docs differing based on delimiters

The koans included showing how ruby can do ‘here docs’ (inline multi-line strings) with ‘flexible quoting’ which made them easier to deal with depending on the content of the string.

However, I was surprised to find it gives you different behavior than what would appear to be the equivalent ‘here doc’ since it keeps the initial newline.

Now, I could see this being intentional since the older ‘here doc’ format has been around for awhile, and for the flexible quoting to not include the first newline would seem very odd to those not thinking of it as another form of ‘here doc’ (since the quoting starts before that first newline, after all), but in terms of showing it as “here’s another way you can do X”, it struck me, at least initially, as odd. :)

If you like Bo Burnham…

I hope this is just some really good troll.  Otherwise, poor Bo Burnham might be going on a RAMPAGE. :)

If anything, I would more expect to see Rucka Rucka Ali listed before Justin Bieber.

Of course, I can’t seem to get Pandora to understand that liking Bo Burnham means I like the music part, since it keeps throwing in regular stand-up acts instead of things like MC Lars, Stephen Lynch or The Lonely Island

image