microsoft / microsoft/TypeScript
typescript version 7 complains about unused generic type even though version 6 does not
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
🔎 Search Terms
"TS6196", "is declared but never used", "unused generic", "noUnusedParameters"
🕗 Version & Regression Information
- This changed between versions 6.0.3 and 7.0.2
⏯ Playground Link
💻 Code
type Ref<T> = {
value: T,
}
function createRef<T,U extends void>(value: void): Ref<T>;
function createRef<T>(value: T): Ref<T>;
function createRef<T>(value: T): Ref<T> {
return {
value,
};
}
const ref1 = createRef();
console.log(ref1);
const ref2 = createRef<number, void>();
console.log(ref2);
const ref3 = createRef<number>(13);
console.log(ref3);
🙁 Actual behavior
The typescript compiler version 7 fails with following error message:
code.ts:5:22 - error TS6196: 'U' is declared but never used.
5 function createRef<T,U extends void>(value: void): Ref<T>;
~~~~~~~~~~~~~~
Found 1 error in code.ts:5
The typescript compiler version 6 succeeds without any errors.
🙂 Expected behavior
The typescript compiler version 7 should behave exactly like version 6 i.e. not fail.
Additional information about the issue
This error only occurs with noUnusedParameters set to true.
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
Reproduce the error from the linked Playground using noUnusedParameters and the shown createRef overloads, then trace the compiler’s handling of unused generic type parameters in overload declarations. Add a regression test covering the version-7 behavior and verify that the example no longer reports TS6196 while other unused-parameter diagnostics remain correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100