It's funny, but a large reason for why Go was chosen was explicitly because it has semantics close to TypeScript and that made it automatable:

https://github.com/microsoft/typescript-go/discussions/411#d...

> But this wasn't a compiler redesign, and the TypeScript to Go move was far more automatable and more one-to-one in its mapping.

So basically the opposite of what you're saying.