We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
current patch use XXX == 'keyword' || XXX == 'trans_keyword' inline to support different languages
XXX == 'keyword' || XXX == 'trans_keyword'
could be replaced by a set of isKeyword[Keyword] function and wrap the matching detail inside of the function
ex, instead of XXX == 'Symbol' || XXX == '中文'
XXX == 'Symbol' || XXX == '中文'
replace to isKeyword(XXX)
isKeyword(XXX)
and define function
function isKeywordSymbol(value) { return value == 'Symbol' || value == '中文' }
The change could be proposed to TypeScript for maintainability.
By replacing the isKeyword[Keyword] functions, LingaScript could even support parse multi-native-language keywords in the same compiler
The text was updated successfully, but these errors were encountered:
first attempt at 3b007cc
Sorry, something went wrong.
66705fe
gasolin
No branches or pull requests
current patch use
XXX == 'keyword' || XXX == 'trans_keyword'
inline to support different languagescould be replaced by a set of isKeyword[Keyword] function and wrap the matching detail inside of the function
ex, instead of
XXX == 'Symbol' || XXX == '中文'
replace to
isKeyword(XXX)
and define function
The change could be proposed to TypeScript for maintainability.
By replacing the isKeyword[Keyword] functions, LingaScript could even support parse multi-native-language keywords in the same compiler
The text was updated successfully, but these errors were encountered: