Allow attr_reader :foo? to define instance method foo? for accessing @foo
Now we should write an accessor method of a boolean instance variable like
def foo? @foo end
But I want to write it by using attr_reader like:
Updated by matz (Yukihiro Matsumoto) over 5 years ago
- Status changed from Open to Rejected
as a rule,
attr_reader x creates an instance variable
@x, but we cannot have
that's the reason, we reject
attr_reader :foo?. If you have any concrete use-case for
the new (more complex) behavior, please tell me.
Updated by svoop (Sven Schwyn) over 4 years ago
If you have any concrete use-case for the new (more complex) behavior, please tell me.
This feature request has been rejected more than once, so I'm most likely doing this in vain. But the obvious use-case would be better readability. Right now, the way to do it is:
class Foobar attr_accessor :color attr_writer :transparent def transparent? @transparent end end
Even though the transparent reader is trivial, it has to be explicitly added and thus is not part of the list of other trivial accessors such as color.
If tailing question marks are ignored when trivial writers are created, the code looks as follows:
class Foobar attr_accessor :color, :transparent? end
The writer remains "transparent=", but it could reject any non-boolean values. The reader would be "transparent" with an alias "transparent?"
It's just a little magic to remove crust. And it wouldn't break any existing code because accessors and writers with tailing question marks raise "invalid attribute name" as of now.