[#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:101452] [Ruby master Feature#17392] Is there any plan to unify the namespace after ruby3
From:
fyjzyyx@...
Date:
2020-12-14 20:30:16 UTC
List:
ruby-core #101452
Issue #17392 has been reported by jackmaple (maple jack).
----------------------------------------
Feature #17392: Is there any plan to unify the namespace after ruby3
https://bugs.ruby-lang.org/issues/17392
* Author: jackmaple (maple jack)
* Status: Open
* Priority: Normal
----------------------------------------
Hello.Currently, methods and variables in ruby are separated (lisp-2 semantics), but few people define variables and methods as the same name, right?
Although some people may do this, should we unify the namespace for the better development of ruby in the future? Does this improve the performance of the language and avoid name confusion.
example:
``` ruby
def foo
puts "ruby method"
end
foo = 3
puts foo # show 3
foo() # call method
```
It doesn't feel very good.But can we add an option switch to ensure compatibility?
``` ruby
use ruby3
def foo
puts "ruby method"
end
foo = 3
puts foo # show 3
foo() # error
```
If we implement a unified namespace, can we call lambda, proc, block and so on without using call, so that the call forms of methods are unified.
``` ruby
use ruby3
def foo x
return x + 1
end
f = -> x {x + 1}
foo 2 # result = 3
f 2 # result = 3
```
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>