microsoft / microsoft/TypeScript

Allow omission of generic type if its equal to the default type

Open
#41,724 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Search Terms

generic, default, extends, equals, =

Suggestion

Allow the syntax extends = T in generics definition in place of extends T = T.

Currently

class Foo <T extends any = any> {}

Suggestion*

class Foo <T extends= any> {}

Use Cases

The problem of having to write <T extends any = any> revealed itself when I had a bit more complex type looking like keyof NetworkTransportProtocol that looked then somehow like this:

class Foo<T extends keyof system.NetworkTransportProtocol = keyof system.NetworkTransportProtocol> {}

which just was a lot of duplicated text.

class Foo<T extends= keyof system.NetworkTransportProtocol> {}

by reducing the duplicate information the whole syntax becomes better to read.

While I did focus on the default-case for class-generics. I believe this could also help with other definitions:

function foo <T extends=any>(bar: T) {}

Checklist

My suggestion meets these guidelines:

  • This wouldn't be a breaking change in existing TypeScript/JavaScript code
  • This wouldn't change the runtime behavior of existing JavaScript code
  • This could be implemented without emitting different JS based on the types of the expressions
  • This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
  • This feature would agree with the rest of TypeScript's Design Goals.

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

The issue does not name implementation files or tests; start by locating TypeScript's grammar and tests for generic constraints and default types. Compare the proposed extends= syntax for class and function generics, then determine the parser and type-checking behavior required. Done would require an accepted design and passing coverage for the proposed syntax.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.