Namespace / mangle type names made global in externs

Currently, a TypeScript file containing ambient declarations writes out a secondary externs file:

declare interface Foo { ... }

Generates an externs.js:

/** @interface */
function Foo() {}

The problem is that Foo in the externs file is a global type, whereas the Foo in the TypeScript file was scoped to the local module. Thus, multiple Foos in multiple files can conflict.

A potential fix would be to namespace/mangle Foo as e.g. _tsickle_extern_path_to_the_file_Foo and then include an alias in the Closure output (something like var Foo = _tsickle_extern_path_to_the_file_Foo;).

[mprobst]

@b-strauss within a goog.module, all symbols, including types, are scoped to the local file, and can only be seen “on the outside” through explicitly exporting them. So there’s no conflict there.

[mprobst]

Fixed a while ago.