* [ruby-core:103320] [CommonRuby Feature#11541] Let attr_accessor, _reader & _writer return symbols of the defined methods
[not found] <redmine.issue-11541.20150920153759.9971@ruby-lang.org>
@ 2021-04-08 22:27 ` marcandre-ruby-core
0 siblings, 0 replies; only message in thread
From: marcandre-ruby-core @ 2021-04-08 22:27 UTC (permalink / raw)
To: ruby-core
Issue #11541 has been updated by marcandre (Marc-Andre Lafortune).
Status changed from Open to Closed
Shipped in Ruby 3.0
----------------------------------------
Feature #11541: Let attr_accessor, _reader & _writer return symbols of the defined methods
https://bugs.ruby-lang.org/issues/11541#change-91408
* Author: iGEL (Johannes Barre)
* Status: Closed
* Priority: Normal
----------------------------------------
Since Ruby 2.1, `def` returns a symbol with the name of the just defined method, so you can easily pass it to visibility modifiers like `private`, `protected`, and `public`. Why not let `attr_reader` & friends return an array with the names of the defined methods, so we can easily write:
~~~
private attr_reader :method1, :method2
~~~
To fully support the example above, `private` would be required to accept also arrays with method names. Without it, it would require the star syntax, which would already be an improvement:
~~~~
private *attr_reader :method1, :method2
~~~~
I wrote two test cases to better illustrate the impact:
~~~~
test/ruby/test_module.rb:
def test_attr_return_value
c = Class.new
assert_equal(%i(reader1 reader2), c.class_eval { attr_reader(:reader1, :reader2) })
assert_equal(%i(writer1= writer2=), c.class_eval { attr_writer(:writer1, :writer2) })
assert_equal(%i(accessor1 accessor1= accessor2 accessor2=), c.class_eval { attr_accessor(:accessor1, :accessor2) })
end
test/ruby/test_method.rb:
def test_visibility_modifier_with_array
c = Class.new do
def m1; end
def m2; end
end
c.class_eval { private %i(m1 m2) }
assert(c.private_method_defined?(:m1))
assert(c.private_method_defined?(:m2))
c.class_eval { protected %w(m1 m2) }
assert(c.protected_method_defined?(:m1))
assert(c.protected_method_defined?(:m2))
c.class_eval { public :m1, [:m2] } # Not sure if this should be allowed.
assert(c.public_method_defined?(:m1))
assert(c.public_method_defined?(:m2))
assert_raise(NameError) do
c.class_eval { private %i(m1 m2 m3) }
end
assert(c.private_method_defined?(:m1))
assert(c.private_method_defined?(:m2))
assert_raise(TypeError) do
c.class_eval { protected [:m1, 2] }
end
assert(c.private_method_defined?(:m1))
assert_raise(TypeError) do
c.class_eval { public [:m1, [:m2]] } # Not sure about this case. Should it be allowed?
end
assert(c.public_method_defined?(:m1))
end
~~~~
WDYT? Thank you!
--
https://bugs.ruby-lang.org/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-04-08 22:27 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <redmine.issue-11541.20150920153759.9971@ruby-lang.org>
2021-04-08 22:27 ` [ruby-core:103320] [CommonRuby Feature#11541] Let attr_accessor, _reader & _writer return symbols of the defined methods marcandre-ruby-core
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).