[#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:101656] [Ruby master Bug#17428] Method#inspect bad output for class methods
From:
merch-redmine@...
Date:
2020-12-23 15:46:02 UTC
List:
ruby-core #101656
Issue #17428 has been updated by jeremyevans0 (Jeremy Evans). Using `#<Class:String>(Module)#` instead of `String(Module).` is a trivial change to make, and I have no preference between the two. `String.(Module#)` is a significantly more invasive change and I don't think we should go that route. It would be great to get feedback from other committers regarding this today if we want this fix to make 3.0. ---------------------------------------- Bug #17428: Method#inspect bad output for class methods https://bugs.ruby-lang.org/issues/17428#change-89445 * Author: marcandre (Marc-Andre Lafortune) * Status: Open * Priority: Normal * Assignee: jeremyevans0 (Jeremy Evans) * ruby -v: ruby 3.0.0dev (2020-12-22T17:37:59Z master 487355873a) [x86_64-darwin18] * Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN ---------------------------------------- ``` $ $ ruby -e 'p String.method(:prepend)' # 2.7.0: #<Method: String.prepend(*)> # 3.0.0: #<Method: #<Class:Object>(Module)#prepend(*)> ``` @jeremyevans found it shows the method as pertaining to one level too high (which is good for objects as we don't want to show the singleton class there, but not for classes). Probably due to #15608 -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>