[#63592] [ruby-trunk - Bug #10009] IO operation is 10x slower in multi-thread environment — normalperson@...
Issue #10009 has been updated by Eric Wong.
3 messages
2014/07/08
[#63682] [ruby-trunk - Feature #10030] [PATCH] reduce rb_iseq_struct to 296 bytes — ko1@...
Issue #10030 has been updated by Koichi Sasada.
3 messages
2014/07/13
[#63703] [ruby-trunk - Feature #10030] [PATCH] reduce rb_iseq_struct to 296 bytes — ko1@...
Issue #10030 has been updated by Koichi Sasada.
3 messages
2014/07/14
[#63743] [ruby-trunk - Bug #10037] Since r46798 on Solaris, "[BUG] rb_vm_get_cref: unreachable" during make — ngotogenome@...
Issue #10037 has been updated by Naohisa Goto.
3 messages
2014/07/15
[#64136] Ruby 2.1.2 (and 2.1.1 and probably others) assumes a libffi with 3 version numbers in extconf.rb — "Jeffrey 'jf' Lim" <jfs.world@...>
As per subject.
4 messages
2014/07/31
[#64138] Re: Ruby 2.1.2 (and 2.1.1 and probably others) assumes a libffi with 3 version numbers in extconf.rb
— "Jeffrey 'jf' Lim" <jfs.world@...>
2014/07/31
On Thu, Jul 31, 2014 at 6:03 PM, Jeffrey 'jf' Lim <[email protected]>
[ruby-core:63808] [ruby-trunk - Feature #10047] [Feedback] Proposal for failesafe requires
From:
matz@...
Date:
2014-07-17 22:35:58 UTC
List:
ruby-core #63808
Issue #10047 has been updated by Yukihiro Matsumoto. Status changed from Open to Feedback If `require` failed, you don't have the features (classes and modules) from the library, so that your program would not work. So I think plain `require_failsafe` is useless. Matz. ---------------------------------------- Feature #10047: Proposal for failesafe requires https://bugs.ruby-lang.org/issues/10047#change-47842 * Author: Robert A. Heiler * Status: Feedback * Priority: Low * Assignee: * Category: * Target version: ---------------------------------------- Hi guys, I know this is unlikely to make it in, so it can be closed soon I suppose, but a short discussion might be useful still? I am doing something like this here quite often: begin require 'foo_bar' rescue LoadError; end One project I use has about 100 of these requires. These projects are mostly tiny, often consisting of just one file, and it also is often not important if these are available or not, hence why there is a silent rescue, so that loading of the main project can continue unhampered. But I wondered why I couldn't just use a special call of require instead. We have require_relative, so why not something like this: require_failsafe 'foo_bar' ? You could even report a string to the user like: require_failsafe 'foo_bar','please install foo_bar' yet continue loading. -- https://bugs.ruby-lang.org/