Repository navigation
Quickinfo incorrectly computes zero-candidate type parameter with contextual inference candidate #44879
Description
Bug Report
🔎 Search Terms
intellisense, contextual inference, call site inference
Related: #44821
🕗 Version & Regression Information
Tested with v4.3.4
⏯ Playground Link
💻 Code
m({ foo: $("foo") }); // unexpected error
declare const m:
<S extends string>(s: { [_ in S]: { $: NoInfer<S> } }) => void
declare const $: <S, T extends S>(s: T) =>
{ $: S }
type NoInfer<T> = [T][T extends any ? 0 : never];🙁 Actual behavior
Code does not compile
🙂 Expected behavior
Code should compile. Especially when the intellisense gets the type parameters right and also provides completions.
Expected type parameters and return type -
Expected completion -
But doesn't compile and gives error -
Activity
[-]Probable bug: Inconsistency between compilation and intellisense in case of contextual inference at call-site[/-][+]Quickinfo incorrectly computes zero-candidate type parameter with contextual inference candidate[/+]RyanCavanaugh commentedon Jul 6, 2021
The compile-time inference is correct. I'm not sure what
$is trying to accomplish, but it's not written in a way that can produce meaningful results -- it says "I take aTand return some supertype of that in$", which doesn't really make any sense.devanshj commentedon Jul 7, 2021
Yeah it was sort of a workaround, it should have simply been
$: <T>(s: T) => { $: T }(the$1version) as you said here.