3 ms·
Hah, let me just chime in with a recent TS error that almost drove me nuts[1]: Type 'Record<string, any>' is not assignable to type 'T'. 'Record<string, an
by 9dev 5y ago
Hah, let me just chime in with a recent TS error that almost drove me nuts[1]:
Type 'Record<string, any>' is not assignable to type 'T'.
'Record<string, any>' is assignable to the constraint of type 'T', but 'T' could be instantiated with a different subtype of constraint 'Record<string, any>'. (2322)
Would you have figured out that the solution to the problem was to omit the - factually correct - return type of the method?
Rust is not just better at error messages, it's playing an entirely different game.
[1]: https://stackoverflow.com/q/67397978/2532203 https://stackoverflow.com/q/67397978/2532203
- azangru 5y ago> Would you have figured out that the solution to the problem was to omit the - factually correct - return type of the method? While I would not be able to figure out the solution to this problem from the error message alone, I would gather from it that typescript is telling me here that it cannot guarantee that it will satisfy the type contract, i.e. that the function will return a thing of the same generic type T as it received. This is useful information in debugging the type declaration of the function.