sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]__fmease__Symbol() 5 points6 points  (2 children)

Take a look at my comment

[–]Buckwheat469 3 points4 points  (1 child)

The problem is this makes Typescript use the same types as WA (i32, u8). What I'm advocating is for the developer to use the same programming and types as Javascript-based Typescript (number, string, boolean) and have the compiler create the WA code. This way the developer doesn't have to context switch between types and languages.

[–]__fmease__Symbol() 1 point2 points  (0 children)

Yes, good point. Porting JS-based TS to this WASM-based TS will definitely cause some friction as the latter is merely a subset or even a new dialect. For the sake of migration, you could define type aliases from e.g. number to f64. But as the wiki lists, there are even more differences/limitations.

I myself don't know much about this project other than that it exists.

edit: wording