Searching for answers in the proper context was difficult pre-AI for some language languages (ex. "Go" vs "Golang" [1]), I wonder if search term collision with the word "script" is going to be better or worse with summarized searches.
[1] The Go language developers at sometime asserted the name was not "Golang", but that produced much better search results.
Very interesting. I made a similar project called tsonic [1] which compiles TS to C# and then uses NativeAOT to compile it down to native code.
We'd have faced similar issues, and I'm curious how you solved it. From your examples:
function add(a: number, b: number): number {
return a + b;
}
The challenge I faced here with JS/TS was that they have a single "number" type which can be carry ints, longs, floats etc. In most application code, you don't want a and b to be floats - you want them to be integers; such as in a loop counter. There are a whole bunch of types in native code that have no equivalent in TS.
It took me several months to get to a usable state, working on issues one by one.
Searching for answers in the proper context was difficult pre-AI for some language languages (ex. "Go" vs "Golang" [1]), I wonder if search term collision with the word "script" is going to be better or worse with summarized searches.
[1] The Go language developers at sometime asserted the name was not "Golang", but that produced much better search results.