[#68137] improve semantics of manpages — "Anthony J. Bentley" <anthony@...>
Hi,
1 message
2015/02/17
[#68144] Re: Future of test suites for Ruby — Anthony Crumley <anthony.crumley@...>
FYI...
4 messages
2015/02/17
[#68343] [Ruby trunk - Bug #10916] [Open] What the Ruby? SegFault? — ruby@...
Issue #10916 has been reported by why do i need this acct just to create a bug report.
5 messages
2015/02/27
[#68373] Re: [Ruby trunk - Bug #10916] [Open] What the Ruby? SegFault?
— "Martin J. Dürst" <duerst@...>
2015/03/02
> * Author: why do i need this acct just to create a bug report
[#68358] [Ruby trunk - Bug #10902] require("enumerator") scans LOAD_PATH 2x on every invocation — ruby@...1.net
Issue #10902 has been updated by Aman Gupta.
3 messages
2015/02/28
[ruby-core:68213] [Ruby trunk - Feature #10879] [Open] UnboundMethod#to_proc
From:
Damien.Olivier.Robert+ruby@...
Date:
2015-02-21 19:56:45 UTC
List:
ruby-core #68213
Issue #10879 has been reported by Damien Robert.
----------------------------------------
Feature #10879: UnboundMethod#to_proc
https://bugs.ruby-lang.org/issues/10879
* Author: Damien Robert
* Status: Open
* Priority: Normal
* Assignee:
----------------------------------------
Since unbound methods from modules can now be bound to any object, I use them a lot.
I think it would be very natural to be able to convert them to Proc:
~~~
module UnboundMethod
def to_proc
return lambda do |obj,*args,&b|
self.bind(obj).call(*args,&b)
end
end
end
~~~
This would allow things like
~~~~
module Foo
def foo
self+"foo"
end
end
["bar","baz"].map(&Foo.instance_method(:foo)) => ["barfoo", "bazfoo"]
~~~~
--
https://bugs.ruby-lang.org/