microsoft / microsoft/TypeScript

Allow custom keywords to make it easy for children in different languages to contact typescript for simple computational experiments

Open
#31,256 2 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

custome keywords

Suggestion

Allow custom keywords to make it easy for children in different languages to contact typescript for simple computational experiments

This requires a keyword standard in different language environments.
Unfortunately, no standardization organization has set standards for it, and because of the inaccuracy of translation, there is not even a recognized standard.

Use Cases

Let children play with programming.
eg:
lingascript (Multilingual Javascript, based on Typescript)
chinese keywords typescript, use cases of chinese keywords typescript
Japanese keyword javascript nadesiko3

Examples

//English
function sum(a:number,b:number):number{
    return a+b;   
}
//Chinese
函数 加和( a:数字, b:数字) :数字{
    返回 a+b
}
//Russian
функция суммировать( a:цифра, b:цифра) :цифра{
    возвращение a+b
}
//Japanese
関数  和を加える( a:数字, b:数字) :数字{
    戻る a+b
}

... etc.

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 names no files, tests, or compiler entry point. Start by determining where TypeScript parses keywords and how localized keyword sets could be specified, then define a concrete supported syntax and tests that show translated examples compile without changing emitted JavaScript.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
compilers, localization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.