Vincent Langlet

Hi @orklah @weirdan. As shown by this PR the current test is wrong `@template TRequestedInstance extends InstanceType` is not a valid syntax and fixing it to `@template TRequestedInstance of InstanceType`...

This test was introduced by https://github.com/vimeo/psalm/pull/10191 I assume the bug you tried to fix is not fully fixed. Any idea how to fix it @boesing ?

> The only error I get now is coming from the test [vimeo/psalm/pull/10927/files/91ea61e4170656cb7a54347271d054e9037106d6#diff-19d1ea03f9fa43528c7190e1c91a6a4f216c48b742e3e2dcdd4e75e750c6a7a5](https://github.com/vimeo/psalm/pull/10927/files/91ea61e4170656cb7a54347271d054e9037106d6#diff-19d1ea03f9fa43528c7190e1c91a6a4f216c48b742e3e2dcdd4e75e750c6a7a5) > > But this failure also happen in 5.x as soon as I fix the phpdoc of...

You should use the `depcheck` library instead. This is the library used by this package.

@dylang This would be great Edit: It seems there is another PR https://github.com/dylang/npm-check/pull/365/files

> Do you think this is a good idea @derrabus? > > I also need to hear from you how you'd approach this and if it's even possible to detect...

> The performance issue is when passing objects, not other types. A general rule forcing type setting is overkill since there is good auto detection and that shortens code. So...

> A very simple rule could emit an error if the third parameter is omitted for a non-scalar value. Yes, that would be great

> > A very simple rule could emit an error if the third parameter is omitted for a non-scalar value. > > But entity is fine, those should be excluded,...

> * Introduce a `non-numeric-string` type. Right now we have `numeric-string` so the opposite should be easy. The only issue is the fact that the cast is only for integer-string,...