TS Spec doesn't match implementation re method signature definitions

[TS Spec § 3.9.5](https://github.com/Microsoft/TypeScript/blob/master/doc/spec.md#395-method-signatures) says: > A method signature of the form >```ts > f < T1, T2, ... > ( p1, p2, ... ) : R >``` >is equivalent to the property declaration >```ts >f : { < T1, T2, ... > ( p1, p2, ... ) : R } >``` But this is not the case with `--strictFunctionTypes`: ```ts interface IFoo1 { bar(baz?: number): void } class Foo1 implements IFoo1 { bar: (baz: number) => void = (n) => void 0; } interface IFoo2 { bar: { (baz?: number): void } } class Foo2 implements IFoo2 { bar: (baz: number) => void = (n) => void 0; // err: Property 'bar' in type 'Foo2' is not assignable to the same property in base type 'IFoo2'. } ``` I understand that the method bivarience in general is intentional as per the [PR](https://github.com/Microsoft/TypeScript/pull/18654): >With this PR we introduce a --strictFunctionTypes mode in which function type parameter positions are checked contravariantly instead of bivariantly. *The stricter checking applies to all function types, except those originating in method or construcor declarations* But it would be nice if the spec didn't state the syntaxes were equivalent when they aren't.