microsoft / microsoft/TypeScript

Add support for using declaration

Open
#30,612 0 comments 0 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

using-declaration, using, declaration, overload

Suggestion

Add language support similar to Using-declaration in C++ (https://en.cppreference.com/w/cpp/language/using_declaration) to pull in names from base class.

Use Cases

In derived class a new overload is added to an API. This requires that overloads from base classes are copied to derived class otherwise typescript complains. A keyword like the using-declaration in C++ to pull in names from base class would be handy to avoid duplication.

Examples

class Emitter {
  addListener(event: "foo", cb: (p: string) => void): void;
  addListener(event: "bar", cb: (p: string, e: number) => void): void;
  addListener(event: string, cb: (...arg: any[]) => void): void {}
}

class SpecialEmitter extends Emitter {
  // I would prefer using Emitter.addListener or similar here
  addListener(event: "foo", cb: (p: string) => void): void;
  addListener(event: "bar", cb: (p: string, e: number) => void): void;

  // new overloads supported by SpecialEmitter
  addListener(event: "new", cb: (x: RegExp) => void): void;
  addListener(event: "next", cb: (x: number, b: boolean) => void): void;
  addListener(event: string, cb: (...arg: any[]) => void): void {}
}

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

No TypeScript source file, test, or entry point is named. Start by reviewing the linked C++ using-declaration reference and the provided inheritance/overload example. Done would require an agreed TypeScript syntax and semantics for reusing base-class names, with tests covering the behavior.

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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.