microsoft / microsoft/TypeScript
Unexpected behavior when static methods are used in an array
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
TypeScript Version: 4.2.0-dev.20201211 (also tested with 4.2.0)
Search Terms: static method(s)
Code
class S {
static f(a: number|string): void {}
}
function g(a: number): void {}
// Uncomment to see a different behavior of the `output` const type.
// type G = typeof g;
const y = [S.f, g];
const output: ((ctrl: number|string) => void)[] = y;
Expected behavior:
Consistent type checking result (an error) for the output const with and without type G = typeof g.
Actual behavior:
If the type G = typeof g is present, the error is thrown (as expected), otherwise there is no error thrown.
Playground Link:
Playground link to reproduce the error.
// cc @alxhub @rkirov
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked TypeScript Playground and the reduced example using S.f, g, and the output assignment. Compare type checking with and without the G alias, then verify the fix by ensuring both versions consistently report the expected error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100