TurboScript
TurboScript copied to clipboard
01alchemist
type number
How about implement general type number for backward compatibility with Typescript?
It may be just alias of float64.
That is a good idea, I was also thinking about it. TurboScript's ultimate goal is to compile pure typescript to WASM. right now i am implementing generic data types for array support which is more important in my readmap. after completing the generics i will add type number. Thanks for the input. 👍
Is the goal really to be a proper super/subset of TypeScript? I think that also means Turbo is JavaScript. This is laudable goal and someone will do it, but is that really the long term goal?
I'd like to suggest creating a wiki page with the long term goals of the project defined up front. It will provide guidance for features and allow newbies to understand the project direction.
My personal goal for TurboScript is to be a superset of TypeScript and keep the JavaScript like syntax.
On Wed 12. Apr 2017 at 4:44 PM, Wink Saville [email protected] wrote:
Is the goal really to be a proper super/subset of TypeScript? I think that also means Turbo is JavaScript. This is laudable goal and someone will do it, but is that really the long term goal?
I'd like to suggest creating a wiki page with the long term goals of the project defined up front. It will provide guidance for features and allow newbies to understand the project direction.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/01alchemist/TurboScript/issues/10#issuecomment-293600115, or mute the thread https://github.com/notifications/unsubscribe-auth/AAMGZogPWktPfwVv0zb3vPCipn4VLdNhks5rvOM7gaJpZM4Mml0g .
Do you want to support prototypal object or class based objects. I'm guessing that class based objects are faster because they are compiled time generated. That would seem to be counter to the need for performance orientation. Is it a requirement to support JavaScript syntax and semantics too?
On Wed, Apr 12, 2017, 8:54 AM Nidin Vinayakan [email protected] wrote:
My personal goal for TurboScript is to be a superset of TypeScript and keep the JavaScript like syntax.
On Wed 12. Apr 2017 at 4:44 PM, Wink Saville [email protected] wrote:
Is the goal really to be a proper super/subset of TypeScript? I think that also means Turbo is JavaScript. This is laudable goal and someone will do it, but is that really the long term goal?
I'd like to suggest creating a wiki page with the long term goals of the project defined up front. It will provide guidance for features and allow newbies to understand the project direction.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/01alchemist/TurboScript/issues/10#issuecomment-293600115 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AAMGZogPWktPfwVv0zb3vPCipn4VLdNhks5rvOM7gaJpZM4Mml0g
.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/01alchemist/TurboScript/issues/10#issuecomment-293623837, or mute the thread https://github.com/notifications/unsubscribe-auth/AA-hHGEYbbQfHhU_ZICS3dn-0DT9RsASks5rvPO_gaJpZM4Mml0g .
Right now I am only thinking about class based objects. Keeping JavaScript dialect is a requirement. When WASM garbage collector ready, supporting pure JavaScript features are not a problem. There is also a typed object proposal for WASM. TurboScript should be able to compile GC code and non-GC code. for now keep everything lite as possible.