Yuki Kokubun
Yuki Kokubun
[Type expression samples from Closure Library](https://gist.github.com/Kuniwak/4302bf186d85f35a18b1111a58f076be)
[Samples from JSDuck](https://gist.github.com/Kuniwak/4302bf186d85f35a18b1111a58f076be#file-jsduck-types).
[Samples from JSDoc3](https://gist.github.com/Kuniwak/4302bf186d85f35a18b1111a58f076be#file-jsdoc-types).
Sorry for my too late reply. We should support the following abnormal situation if we can: ```vim ::::: \scriptencoding utf8 ``` How do you feel about it?
@thinca I have a question. What is a severity of the rule? For example, Vint has three levels of the severity: Error This code is determinately wrong / This code...
@thinca I have an additional question. I don't know why trailing space in map leads to errors. Could you explain me please?
Hmm, I think the severity of the rule is Style Problem. Because trailing white spaces cannot be cause of errors at that time. But I think this rule is useful....
@bstaletic Thanks for the report. I want to see the error occurred. Could you show me the error message, please?
I confirmed the problem. But I think this cause is in vim-vimlparse. ``` vint._bundles.vimlparser.VimLParserException: vimlparser: E492: Not an editor command: import os: line 3 col 1 ``` I reported this...
Both problems can be caused by the traversing function. In my guess, the function do not visit the variable expression node in `l:{x}` and `call('s:foo')`. I'm gonna add unit tests...