"compute language availability" always returns "unavailable"?

[nathanmemmott]

Might be misreading this, but it looks like the steps for "compute language availability" will only ever return "unavailable". We should hit 2. Return "unavailable" only when a bestMatch is never found, but that Break will trigger it as well.

[domenic]

Good catch. I think this is just a single level of mis-nesting. Let me post a fix and you can double-check my reasoning.

Edit: well, "a single level of mis-nesting" is not really a good way to describe it. Anyway, the post-a-fix with you double-checking strategy still applies.