We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
王垠抨击过缩进语法。其中提到缩进很容易在编辑的时候弄坏,比如不小心(猫跳到键盘上?)输入或删去一些空格。而传统语法没有这个问题是因为恰好输入或删除成对的符号(花括号对或begin/end对)的概率小多了。比较来说,缩进是单点变更就会产生语义差异,因而危险。
需要承认这是一个合理的责难。其实可以和 rm -rf / temp 的空格惨案相类比。紧凑的语法往往造成这种问题。
rm -rf / temp
不过实践上似乎并未看到或听到很多实际的惨案,即使coffee、yaml已经相当普及。
有一些方法来克服这一问题:
/
The text was updated successfully, but these errors were encountered:
No branches or pull requests
王垠抨击过缩进语法。其中提到缩进很容易在编辑的时候弄坏,比如不小心(猫跳到键盘上?)输入或删去一些空格。而传统语法没有这个问题是因为恰好输入或删除成对的符号(花括号对或begin/end对)的概率小多了。比较来说,缩进是单点变更就会产生语义差异,因而危险。
需要承认这是一个合理的责难。其实可以和
rm -rf / temp
的空格惨案相类比。紧凑的语法往往造成这种问题。不过实践上似乎并未看到或听到很多实际的惨案,即使coffee、yaml已经相当普及。
有一些方法来克服这一问题:
/
的terminatorThe text was updated successfully, but these errors were encountered: