You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unlike #585 , removing the parentheses would not affect Ruby's ability to parse the code, but if parentheses were removed, programmers may be confused as to whether the {} represents a hash, or a block.
So far, I don't have any good use case scenarios as to why someone should write such code, so I don't know if it's worth fixing, but I wanted to let you know.
The text was updated successfully, but these errors were encountered:
The following code
would fall foul of the MethodCallParentheses cop.
Unlike #585 , removing the parentheses would not affect Ruby's ability to parse the code, but if parentheses were removed, programmers may be confused as to whether the
{}
represents a hash, or a block.So far, I don't have any good use case scenarios as to why someone should write such code, so I don't know if it's worth fixing, but I wanted to let you know.
The text was updated successfully, but these errors were encountered: