Migrate `String` to `StringPrototype`, `Number` to `NumberPrototype`, etc

Suggestion

🔍 Search Terms

string prototype object number stringprototype

✅ Viability 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, new syntax sugar for JS, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

We're always seeing people writing String, Number, Object, and so on, in places where they should be writing their primitive equivalents.

We should mark these as @deprecated so that they show up with strikethroughs in the editor, and make new global interfaces named e.g. StringPrototype so it's more clear what they're for.

/**
 * @deprecated Use `string` when working with strings, or use `StringPrototype` to declare new string methods
 */
interface String {

For back compat, possibly forever, we'll need to declare these as

interface StringPrototype extends String { }

so that existing references to String["charAt"] continue to work and so that other merges continue to function.

📃 Motivating Example

💻 Use Cases

• New users coming to TS

この issue では、ファイル、テスト、エントリポイントのいずれも指定されていません。まず、提案されているグローバルインターフェースの変更と、リンクされた TypeScript の設計目標を確認してください。完了の条件は、既存の参照を壊すことなく、非推奨のラッパーインターフェースと、StringPrototype、NumberPrototype、および関連する宣言に互換性のある宣言が用意されていることです。