microsoft / microsoft/TypeScript
Imperative type definition
还没有人认领这个 Issue。
- 主要语言
- Go
- 星标
- 111k
- 派生
- 14.3k
- 平均合并
- 2 天 4 小时
- 30 天内合并 PR
- 132
描述
### 🔍 Search Terms
imperative typescript interface
### ✅ Viability Checklist
- [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [x] This wouldn't change the runtime behavior of existing JavaScript code
- [x] This could be implemented without emitting different JS based on the types of the expressions
- [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [x] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [x] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals
### ⭐ Suggestion
I work on a library that requires to use lots of 3rd party generic types, multiple mappings and more or less complex typing, and I've got to repeat one complex type multiple times or create another generic that is going to contain a lot of parameters and will complicate the code that's already complicated.
(these types have bugs, they just an illustration)
### 📃 Motivating Example
I imagine it as an "type function" that has function body that returns any valid type.
```ts
imperative type Foo {
type X = Bar;
type Y = Baz;
return { x: X, y: Y };
}
type Quix = Foo;
// Quix { x: Bar, y: Baz }
// ... vs
interface Foo {
x: Bar;
y: Baz;
}
```
### 💻 Use Cases
- Imperative style
- Shorter syntax for complex types
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
未确定实现文件、入口点或测试。首先根据 TypeScript 的设计目标审查提议的语法和动机示例,然后检查类型检查器架构,以确定此类类型级功能适合放置在哪里;完成的要求是达成一致的设计,并有相应的实现和测试。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- typescript
- 领域
- compilers
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100