Chromium Code Reviews
DescriptionFix Chrome-specific closure pass for cr.exportPath()
It thought cr.exportPath() should only take 1 argument
and that this one argument should only be a 'string literal'.
That's just wrong. It was never right. exportPath() takes
up to 3 parameters, 2 of them optional (just uncommon).
This is blocking folks that want to compile code that uses
cr.exportPath() to extend an object other than window or
pass a path that's a variable and not a 'string literal'.
R=tbreisacher@chromium.org
BUG=none
TEST=compiler_test.py
Committed: https://crrev.com/c08acb6c078b8f58c842ee4ec8aa96ea120a91c9
Cr-Commit-Position: refs/heads/master@{#346260}
Patch Set 1 : remove dependent patchset #Patch Set 2 : nit #
Messages
Total messages: 10 (2 generated)
|
|||||||||||||||||||||||||||||||||||||