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.