!can? v.s. cannot? #1

Closed
KieranP opened this Issue Nov 17, 2009 · 5 comments

Projects

None yet

3 participants

@KieranP
KieranP commented Nov 17, 2009

Any reason why you opted to go with !can? rather than a cannot? method?

def cannot?(*args)
  !can?(*args)
end

??

@ryanb
Owner
ryanb commented Nov 17, 2009

I will likely add the cannot? method sometime in the future, but I wanted to work with the library a little bit more to ensure it is the best thing. Thanks for the suggestion!

@ryanb
Owner
ryanb commented Nov 17, 2009

adding 'cannot?' method which performs opposite check of 'can?' - closed by 0f49b54

@mschneider

shouldn't it be can_not? like should_not in rspec?

@ryanb
Owner
ryanb commented Dec 11, 2010

"cannot" is a word in english so I prefer it. The difference with rspec is "shouldnot" is not a word.

@mschneider

I didn't know that cannot was a word. Your point is completely valid :)

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment