blocks|key|1459789|text|我想我两者都做了，但如果增加可读性并避免看起来模棱两可的语句，我肯定会保留它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1459790|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I guess I do both, but I definitely keep them in if it adds to readability and avoids statements that look ambiguous.

blocks|key|1675035|text|通常以可读性较高者为准。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1675036|但是，当我在其他函数的参数中嵌套函数调用时，我总是使用圆括号|1675037|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Whichever is more readable usually.

But I always use parentheses when I'm nesting function calls inside other ones' parameters

blocks|key|1460000|text|如果你的意思是在函数调用中，我总是放在括号里，因为它总是更容易阅读。如果你的意思是在条件(+If，while)中，我只在必要的时候加括号。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1460001|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you mean in function calls, I always put parenthesis because it's always easier to read. If you mean in conditions (if, while) I only put parenthesis when they're necessary.

blocks|key|1460062|text|如果可能的话，我尽量把它们去掉。我认为它使代码更容易阅读(一般来说)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1460063|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I try to leave them out, if at all possible. I think it makes code easier to read (generally speaking).

blocks|key|1460148|text|当我在做DSL之类的事情时，比如rails中的t.column或has_many，我会把它们省略掉。在其他时间，它通常归结为清晰度，它可能是一个均匀的分裂。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1460149|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I leave them out when I'm doing DSL-ish stuff, like t.column or has_many in rails. The rest of the time, it generally comes down to clarity, and it's probably an even split.

blocks|key|1675360|text|在做诸如assert_equal之类的断言时，我倾向于省略它们。也许是为了让它更像领域特定的语言。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1675361|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I tend to leave them out when doing assertions such as assert_equal. Maybe it's to make it domain specific language-like.

blocks|key|1675430|text|我使用括号作为注释来帮助未来的我...谁的脑细胞可能比现在的我少:-)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1675431|没有什么比看你2年前写的一些代码并误解它更糟糕的了，所以你在修改它的时候破坏了它。|1675432|如果parens可以节省我未来几分钟(或几个小时)的时间，我将尽可能多地输入以使语句清晰。|1675433|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I use parens as comments to help the future me... who is likely to have fewer brain cells than the current me :-)

Nothing worse than looking at some code you wrote 2 years ago and misunderstanding it, so that you break something while modifying it. 

If parens will save the future me a few minutes (or hours) in the future, I'll put in as many as needed to make the statement crystal clear.

blocks|key|1675473|text|如果你有很长一段时间的编程经验，你可能会“渴望”添加括号，在很多情况下，这是有充分理由的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1675474|但在我看来，代码看起来更简单，而且我还没有遇到问题--如果您需要使用括号，那么在遇到调试脚本之前，您就会提前知道这一点。|1675475|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If you've been programming for a long time, you'll probably have an "itch" to add parentheses, and in many cases there are good reasons for this.

The code is easier on the eyes though in my opinion, and I haven't run into a problem yet--if you're going to need parentheses, you'll know it beforehand before you have to run into the debugging script.

When possible.. do you leave parentheses in or out in Ruby?

Do you leave parentheses in or out in Ruby?

如果可能的话..在Ruby中，你是把括号放在里面还是放在外面？

问在Ruby中，你是把括号放在里面还是放在外面？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Ruby中，你是把括号放在里面还是放在外面？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Ruby中，你是把括号放在里面还是放在外面？
EN