在方法名称的末尾加上“ !”和“ ?”的目的是什么？

有时候我在 Ruby 中看到方法的末尾有“ ?”和“ !”，例如:

name = "sample_string"
name.reverse
name.reverse!
name.is_binary_data?

我想知道他们的目的是什么? 他们只是语法糖衣？

51747 次浏览
小开

Question mark indicates that the method returns boolean. Already answered here:

What does the question mark operator mean in Ruby?

The bang indicates that the method acts on the object itself. Already answered here:

Why are exclamation marks used in Ruby methods?

小开
最佳答案

It's "just sugarcoating" for readability, but they do have common meanings:

  • Methods ending in ! perform some permanent or potentially dangerous change; for example:
    • Enumerable#sort returns a sorted version of the object while Enumerable#sort! sorts it in place.
    • In Rails, ActiveRecord::Base#save returns false if saving failed, while ActiveRecord::Base#save! raises an exception.
    • Kernel::exit causes a script to exit, while Kernel::exit! does so immediately, bypassing any exit handlers.
  • Methods ending in ? return a boolean, which makes the code flow even more intuitively like a sentence — if number.zero? reads like "if the number is zero", but if number.zero just looks weird.

In your example, name.reverse evaluates to a reversed string, but only after the name.reverse! line does the name variable actually contain the reversed name. name.is_binary_data? looks like "is name binary data?".

小开

In Ruby the ? means that the method is going to return a boolean and the ! modifies the object it was called on. They are there to improve readability when looking at the code.

小开

In contrast to the – I suppose – majority of programming languages ...

Ruby, methods are allowed to end with question marks or exclamation marks.

By convention, methods that answer questions (i.e. Array#empty? returns true if the receiver is empty) end in question marks.

Potentially “dangerous” methods (ie methods that modify self or the arguments, exit! etc.) by convention end with exclamation marks.

From: http://www.ruby-lang.org/en/documentation/ruby-from-other-languages/, Section Funny method names

小开

Beware, this isn't always the case. Take for example, Ruby Array#concat http://docs.ruby-lang.org/en/2.0.0/Array.html#method-i-concat.

Where you can get burnt badly is something like MyActiveRecordModel.column_names.concat([url]). Later calls related to MyActiveRecordModel will try to look for a column of 'url' for MyActiveRecordModel and throw.

Instead you must clone it before doing the concat. Fortunately my test suite caught this one, but.. heads up!


提交答案