Type discrimination in function calls for callable types doesn't work if discriminating property is optional

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨 Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section! Please help us by doing the following steps before logging an issue: * Search: https://github.com/Microsoft/TypeScript/search?type=Issues * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ Please fill in the *entire* template below. --> <!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. --> **TypeScript Version:** 3.7.0-dev.20191015 <!-- Search terms you tried before logging this (so others can find this issue more easily) --> **Search Terms:** type discrimination, callable, signatures, implicit any **Code** ```ts function test( a: | { type?: 1; property: (a: number) => void } | { type: 2; property: (a: string) => void }, ) { return a.property } test({ property: (x) => { // complaining that x implicitly has type any console.log('hi') }, }) ``` **Expected behavior:** `x` should be inferred to be `number`. **Actual behavior:** `x` is `any`. If you change `type?: 1` to `type: 1`, it works as expected. **Playground Link:** [link](http://www.typescriptlang.org/play/index.html#code/GYVwdgxgLglg9mABFApgZygCgFCMQQwC5c9EAfRAb2QE8AHFAfkMQEYBuROgJzge6g0WmIojAgAtgCMU3AJSIAvAD5EANzgwAJogC+JPBWqCGLAEycefWYOGiM3GGADmCles07dAGmwLKJNwoUCDcSPgAdFb8gtj62NioGJgBeNE2QoiYAB5uqtQA9AWIEHASdAA2+E5OzsgAFvhQiNmIMOUVMBAwUBU0iI1otAwEYDQGJQhocBUoERVwzpgA5PUwy3IkPnFyQA) **Related Issues:** #7294 (closed with #29011 - see second half of the original post, I believe it describes why this issue occurs)