Google Feedback on TypeScript 3.5

Hopefully they don’t take the suggested approach of forcing everyone to explicitly write the generic types when creating new Sets/Maps/etc. I realize the type systems are very different under the hood, but if flow can handle this elegantly I would hope that typescript could as well. https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoVBjGBDAzrsAYTAG9U...

Interesting to get a glimpse at Google's usage of Typescript and the problems they encounter when upgrading.

I imagine scenarios like these can happen more often in Google's monorepo when upgrading a widely used tool, library or language? Does Google use this approach (one set of flags, etc. for a compiler for the entire repo) for other languages too?