microsoft / microsoft/TypeScript

Bug with resolveClassOrInterfaceMembers

Open
#3,539 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Help Wanted Suggestion
Dominant language
Go
Stars
111k
Forks
14.3k
Avg merge
2d 4h
Merged PRs (30d)
132

Description

https://github.com/Microsoft/TypeScript/blob/6db4faf4883636e70ef7a99401b9dbc5d1a58631/src/compiler/checker.ts#L2894

interface monster {
    (a: "a"): void;
    (b: "b"): void;
    (c: "c"): void;
    (d: "d"): void;
    (e: "e"): void;
    (x: string): void;
}

interface m1 extends monster {
    a();
}
interface m2 extends monster {
    b();
}
interface m3 extends monster { }
interface m4 extends monster { }

interface m5 extends m1, m2, m3, m4 { }

var waa: m5;
waa("a")

The compiler finds 24 call expressions because it appends 'monster' from each base type.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in src/compiler/checker.ts at the linked resolveClassOrInterfaceMembers location and reproduce the issue with the interface hierarchy and call expression shown here. Trace how members from the repeated base type are collected, then verify that the compiler no longer reports 24 call expressions for the example.

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
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.