Stephen Hicks
Stephen Hicks
Fixes #584 This is safe unless the code is relying on non-standard properties being defined on Object.prototype, which is why the optimization is protected behind the "unsafe" option. Enabling this...
depswriter.py cannot write the new deps.js format, since it cannot parse language version. We should either (a) port it to node.js and publish a tool on NPM, or (b) add...
Peephole passes and others should not traverse into functions annotated with 'use asm'. The 'use asm' string needs to be retained.
While it's a non-goal of Closure Compiler to interoperate with code transpiled by different transpilers (there's simply no reliable way to guarantee this), it should at least be the case...
I tried using the element in my own app but had difficulty. I bisected against the demo and found that if I don't add ``` css :host { @apply(--layout-fullbleed); @apply(--layout-vertical);...
The type registry is not structured for multithreading, so until this access is removed, threading is effectively forbidden here.
The primary use here is "private constructors", which currently are not well-supported by Closure Compiler. One way to fake this is by adding an extra parameter to the constructor, so...
The doc generated for the following code is not particularly useful ```js goog.module('ns.Foo'); class Foo { /** @return {!Builder} */ static builder() { return new Builder(); } } class Builder...
While it's important that package-private (and even private) types be documented, it would be nice if they could be hidden by default. I'm trying to generate API documentation and my...
The following ```js goog.module('ns.Foo'); class Foo {} Foo.Bar = class Bar {}; exports = Foo; ``` produces three classes in the types list: `ns.Foo`, `ns.Foo.Bar`, and `ns.Foo.sdecl$var0`. The third is...