[#101179] Spectre Mitigations — Amel <amel.smajic@...>
Hi there!
5 messages
2020/12/01
[#101180] Re: Spectre Mitigations
— Chris Seaton <chris@...>
2020/12/01
I wouldn’t recommend using Ruby to run in-process untrusted code in the first place. Are people doing that?
[#101694] Ruby 3.0.0 Released — "NARUSE, Yui" <naruse@...>
We are pleased to announce the release of Ruby 3.0.0. From 2015 we
4 messages
2020/12/25
[ruby-core:101366] [Ruby master Feature#17314] Provide a way to declare visibility of attributes defined by attr* methods in a single expression
From:
matz@...
Date:
2020-12-10 07:58:42 UTC
List:
ruby-core #101366
Issue #17314 has been updated by matz (Yukihiro Matsumoto).
I have a small concern about compatibility. But basically agree. Go ahead.
Matz.
----------------------------------------
Feature #17314: Provide a way to declare visibility of attributes defined by attr* methods in a single expression
https://bugs.ruby-lang.org/issues/17314#change-89073
* Author: radarek (RadosナＢw BuナＢt)
* Status: Open
* Priority: Normal
----------------------------------------
**Description**
Many of us (me included) declare class attributes, even if they are private, on the top of class definition. When reading source code it's convinient to see what kind of attributes class has.
To declare private attributes we can:
* declare them with one of `attr*` methods and later change visiblity calling `private`
* call `private` without argument, then declare attributes and finally call (in most cases) `public` to keep defining public methods
* declare attribute on top of the class but make them private in private section later in a file
``` ruby
clsss Foo
attr_accessor :foo
private :foo, :foo= # we have to remember about :foo= too
private
attr_accessor :bar
public
# rest of the code
end
```
To simplify it and create other possibilites I propose to:
* change `attr*` methods so as they return array of defined methods names
* allow `public/protected/private` methods to receive array of methods names (single argument)
With requested feature we could write code like this:
``` ruby
class Foo
private attr_accessor :foo, :bar
end
```
Additionaly you could use `attr*` with your own methods. Something like this:
``` ruby
class Module
def traceable(names)
# ...
names
end
end
class Foo
traceable attr_accessor :foo
# it can be mixed with public/protected/private too
protected traceable attr_accessor :bar
end
```
**Backward compatibility**
* `attr*` methods currently return `nil` so there should be no problem with changing them
* `public/protected/private` methods receive multiple positional arguments and convert all non symbol/string objects to strings. I can imagine only one case where compatibility would be broken:
``` ruby
class Foo
def foo; end
def bar; end
arr = [:foo]
def arr.to_str
'bar'
end
private arr
end
p [Foo.public_instance_methods(false), Foo.private_instance_methods(false)]
```
Currently `[[:foo], [:bar]]` would be displayed, `[[:bar], [:foo]]` after requested feature is implemented.
**Implementation**
You can view my implementation in this (draft) PR: https://github.com/ruby/ruby/pull/3757
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>