[Errors] No error for function with return type annotation that lacks a return statement about typescript

[RyanCavanaugh]

Per CR comments, the fix breaks this (bad) code from 1.0:

class C { get f() { return; } }

[DanielRosenwasser]

To be clear, the old compiler was okay with

function foo(): number {
    return;
}

as well.

Well, I wouldn't say that fixing this bug is a breaking change; rather, I misunderstood the issue with this bug in Pull Request #147. I thought that we should be looking for return expressions rather than statements; however, I think it's worth asking if that's the correct behavior.

from typescript.

[DanielRosenwasser]

I've opened up #162 to discuss this.