3 ms·
> That being said though, I'd expect that a tuple would satisfy a `any[]` type. You have it backwards, the error in question is complaining that `any[]` does n
by rraval 7y ago
> That being said though, I'd expect that a tuple would satisfy a `any[]` type.
You have it backwards, the error in question is complaining that `any[]` does not satisfy the tuple type.
Minimal repro:
function f(x: any[]): [number, string] {
return x;
}
The error matches yours:
Type 'any[]' is missing the following properties from type '[number, string]': 0, 1
From poking the playground, `any[]` hasn't been assignable to tuples since at least v3.3.3
My guess is that the compiler got smarter around reasoning about your `SinonSub` generic and is now forcing you to deal with lingering unsoundness.
- dstaley 7y agoYeah, that's my assumption as well. It would explain why there's no mention of it in breaking changes, and why being specific about the generics in `SinonStub` fixes the error. Makes me wonder what other unsoundness the compiler isn't catching.