microsoft / microsoft/TypeScript

No error on self-referencing type parameter of non-generic mapped type

Open
#62,176 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug Domain: Mapped Types Help Wanted
Dominant language
Go
Stars
111k
Forks
14.3k
Avg merge
2d 4h
Merged PRs (30d)
132

Description

🔎 Search Terms

mapped type circular self reference type parameter

🕗 Version & Regression Information
  • This is the behavior in every version I tried
⏯ Playground Link

https://www.typescriptlang.org/play/?ts=6.0.0-dev.20250801#code/C4TwDgpgBAKhDOwoF4oGsIgPYDMoG8AoKKAbQAUoBLAO3U1ynIF0AuKAVxrRqwHcahAL4BuQoQAmEAMYAbAIYAnaNKw1EUYAmDs4iMYQgAPMFkVIcXacCpqoAcwjA9wABQBKAsSjLgHRXRa+sKEQA

💻 Code
type Test = keyof {
  [P in keyof P]: unknown
};

declare const test: Test;

export function getTest() {
  return test;
}
🙁 Actual behavior

[P in keyof P] doesn't error anyhow but it's clearly circular. Furthermore, the generated .d.ts here is:

export declare function getTest(): keyof P;

P leaked here and this is invalid

🙂 Expected behavior

I'd expect this to produce a circularity error and at the very least the generated declaration file should not contain a leaked type variable

Additional information about the issue

cc @jfet97 who originally mentioned part of this to me in a DM 😉

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 with the linked TypeScript Playground repro and verify both the missing circularity diagnostic and the leaked P in the generated declaration. Trace how the compiler handles [P in keyof P] and declaration output for this case. Done means the circular reference is reported and the emitted declaration contains no leaked type variable.

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
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.