Repository navigation
Fix inference for contextually typed parameters with initializers - #29576
Conversation
|
|
||
| // Use the type of the initializer expression if one is present and the declaration is | ||
| // not a parameter of a contextually typed function | ||
| if (declaration.initializer && !isParameterOfContextuallyTypedFunction) { |
There was a problem hiding this comment.
Wouldn't we rather write declaration.initializer && !(declaration.kind === SyntaxKind.Parameter && getContextualType(<Expression>declaration.parent)) so we only call getContextualType if we absolutely need to?
There was a problem hiding this comment.
Or, since it's used below, write
const needsShapeAndIsNotParameterOfContextuallyTypedFunction = (declaration.initializer || isBindingPattern(declaration.name)) && !(declaration.kind === SyntaxKind.Parameter && getContextualType(<Expression>declaration.parent));There was a problem hiding this comment.
Yeah, possibly. The value is precomputed because I use it in two locations. But I supposed I could turn it into a function that we only call when appropriate.
| declare function id5<T extends (x?: number) => any>(input: T): T; | ||
|
|
||
| const f10 = function ({ foo = 42 }) { return foo }; | ||
| const f11 = id1(function ({ foo = 42 }) { return foo }); // Implicit any error |
There was a problem hiding this comment.
Should we also have a fourslash test for each of these so we can have tests simulating hovering over the different parts in different orders?
| const f10 = function ({ foo = 42 }) { return foo }; | ||
| const f11 = id1(function ({ foo = 42 }) { return foo }); // Implicit any error | ||
| ~~~~~~~~~~~~ | ||
| !!! error TS7022: '{ foo = 42 }' implicitly has type 'any' because it does not have a type annotation and is referenced directly or indirectly in its own initializer. |
There was a problem hiding this comment.
How does this binding pattern circularly reference itself? o.O
There was a problem hiding this comment.
Hmm, strange. This error is caused by declaration file emit, it only appears with --declaration. Have no idea why.
There was a problem hiding this comment.
getEmitDeclarations causes us to conditionally collectLinkedAliases on exported names - but this is a binding pattern in an anonymous function expression, not an exported name... o.O
There was a problem hiding this comment.
Maybe we generate the error while looking up the type of the expression for emitting declare const f11: something? We marked foo as implicitly any within the checker, however did we propagate that up to the binding pattern as a whole?
There was a problem hiding this comment.
The circularity error is caused by the parameter having itself as its contextual type. It's actually unrelated to this PR. For example, this causes the same error on master:
declare function id<T>(input: T): T;
const f1 = id(function ({ foo }) { return foo });# Conflicts: # src/compiler/checker.ts
Fixes #28816.