[#83096] File.setuid? on IO (Re: [ruby-cvs:67289] normal:r60108 (trunk): file.c: release GVL in File.{setuid?, setgid?, sticky?}) — Nobuyoshi Nakada <nobu@...>
On 2017/10/04 8:47, [email protected] wrote:
5 messages
2017/10/04
[#83100] Re: File.setuid? on IO (Re: [ruby-cvs:67289] normal:r60108 (trunk): file.c: release GVL in File.{setuid?, setgid?, sticky?})
— Eric Wong <normalperson@...>
2017/10/04
Nobuyoshi Nakada <[email protected]> wrote:
[#83105] Re: File.setuid? on IO (Re: [ruby-cvs:67289] normal:r60108 (trunk): file.c: release GVL in File.{setuid?, setgid?, sticky?})
— Nobuyoshi Nakada <nobu@...>
2017/10/04
On 2017/10/04 15:55, Eric Wong wrote:
[#83107] Alias Enumerable#include? to Enumerable#includes? — Alberto Almagro <albertoalmagro@...>
Hello,
9 messages
2017/10/04
[#83113] Re: Alias Enumerable#include? to Enumerable#includes?
— "Urabe, Shyouhei" <shyouhei@...>
2017/10/05
This has been requested countless times, then rejected each and every time.
[#83129] Re: Alias Enumerable#include? to Enumerable#includes?
— Alberto Almagro <albertoalmagro@...>
2017/10/05
Sorry I didn't found it on the core mail list's archive.
[#83138] Re: Alias Enumerable#include? to Enumerable#includes?
— "Urabe, Shyouhei" <shyouhei@...>
2017/10/06
Ruby has not been made of popular votes so far. You have to show us
[#83149] Re: Alias Enumerable#include? to Enumerable#includes?
— Eric Wong <normalperson@...>
2017/10/06
Alberto Almagro <[email protected]> wrote:
[#83200] [Ruby trunk Feature#13996] [PATCH] file.c: apply2files releases GVL — normalperson@...
Issue #13996 has been reported by normalperson (Eric Wong).
4 messages
2017/10/10
[ruby-core:83241] [Ruby trunk Bug#14010] RubyVM logic in forwardable backported to 2.3, not removed
From:
headius@...
Date:
2017-10-12 18:49:09 UTC
List:
ruby-core #83241
Issue #14010 has been reported by headius (Charles Nutter). ---------------------------------------- Bug #14010: RubyVM logic in forwardable backported to 2.3, not removed https://bugs.ruby-lang.org/issues/14010 * Author: headius (Charles Nutter) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: 2.3.5 * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN ---------------------------------------- Logic was added to forwardable.rb in at least one commit, and revised in others: https://github.com/ruby/ruby/commit/6fd18ca51bbce302865d23632b15af53d3e8f11b On trunk, this logic was eventually replaced with code that works on Ruby impls other than MRI: https://github.com/ruby/ruby/commit/2283d14cc9fefa278dfde02bdf8d84ce50cfe16f I request that RubyVM not ever be used in stdlib unless guarded with a RUBY_ENGINE check plus fallback code. It is not possible for any implementation other than MRI to support RubyVM::InstructionSequence and whenever it is used in tests or stdlib we have to patch around it. Please backport the remaining changes to forwardable to the ruby-2_3 branch for release, so we can return to using the stock forwardable.rb in JRuby. Thank you! -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>