google/closure-compiler

Closure compiler fails to parse "interface" as parameter name

Open

#2,852 创建于 2018年3月15日

在 GitHub 查看
 (2 评论) (1 反应) (0 负责人)Java (7,176 star) (1,197 fork)batch import
P3Parserhelp wanted

描述

Closure compiler is unable to parse "interface" being used as the name of a parameter. This code does successfully execute in Chrome, Safari, and Firefox devtools.

(function x(interface) { console.log(interface); })('test')

https://closure-compiler.appspot.com/home#code%3D%252F%252F%2520%253D%253DClosureCompiler%253D%253D%250A%252F%252F%2520%2540compilation_level%2520ADVANCED_OPTIMIZATIONS%250A%252F%252F%2520%2540output_file_name%2520default.js%250A%252F%252F%2520%2540formatting%2520pretty_print%250A%252F%252F%2520%253D%253D%252FClosureCompiler%253D%253D%250A%250A(function%2520x(interface)%2520%257B%2520console.log(interface)%253B%2520%257D)('test')

贡献者指南

技术栈
javascriptjava
领域
tooling
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
basic JavaScriptunderstanding of parsers
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
Investigate the Closure Compiler parser code, likely in files like JsDocInfoParser.java or JSTypeRegistry.java, to identify where 'interface' is incorrectly treated as a reserved keyword. Check the list of reserved words and ensure that parameter names are allowed to be 'interface'. Look at how other reserved words that are not actually reserved in JavaScript (e.g., 'int') are handled.