[#80974] [Ruby trunk Feature#13517] [PATCH] reduce rb_mutex_t size from 160 to 80 bytes on 64-bit — ko1@...
Issue #13517 has been updated by ko1 (Koichi Sasada).
4 messages
2017/05/02
[#81024] Re: [Ruby trunk Feature#13517] [PATCH] reduce rb_mutex_t size from 160 to 80 bytes on 64-bit
— SASADA Koichi <ko1@...>
2017/05/07
sorry for late response.
[#80996] [Ruby trunk Feature#13544] Allow loading an ISeqs sequence directly from a C extension without requiring buffer is in an RVALUE — sam.saffron@...
Issue #13544 has been reported by sam.saffron (Sam Saffron).
3 messages
2017/05/04
[#81016] [Ruby trunk Bug#13526] Segmentation fault at 0x0055c2e58e8920 ruby 2.3.1p112 (2016-04-26 revision 54768) [x86_64-linux] — s.wanabe@...
Issue #13526 has been updated by wanabe (_ wanabe).
3 messages
2017/05/07
[#81048] Re: [ruby-cvs:65788] normal:r58614 (trunk): rb_execution_context_t: move stack, stack_size and cfp from rb_thread_t — SASADA Koichi <ko1@...>
It causes compile error on raspi 3.
3 messages
2017/05/09
[#81201] Re: [ruby-cvs:65935] normal:r58761 (trunk): test/test_extilibs.rb: do not check the existence of fiddle — "U.NAKAMURA" <usa@...>
Hi, Eric
4 messages
2017/05/16
[#81202] Re: [ruby-cvs:65935] normal:r58761 (trunk): test/test_extilibs.rb: do not check the existence of fiddle
— Eric Wong <normalperson@...>
2017/05/16
"U.NAKAMURA" <usa@garbagecollect.jp> wrote:
[#81427] Fwd: [ruby-changes:46809] normal:r58924 (trunk): test for IO.copy_stream CPU usage (r58534) — SASADA Koichi <ko1@...>
Hi,
6 messages
2017/05/28
[#81428] Re: Fwd: [ruby-changes:46809] normal:r58924 (trunk): test for IO.copy_stream CPU usage (r58534)
— Eric Wong <normalperson@...>
2017/05/28
SASADA Koichi <ko1@atdot.net> wrote:
[ruby-core:81141] [Ruby trunk Feature#13559] Change implementation of Feature #6721
From:
zverok.offline@...
Date:
2017-05-13 13:50:40 UTC
List:
ruby-core #81141
Issue #13559 has been updated by zverok (Victor Shepelev).
To be honest, the selected name for the method dozens of peoples wanted for 5 years looks really bad.
It is like instead of `map` Ruby'd had a method named like, I don't know, `yield_each_and_return_result`.
I always believed Ruby's method names are carefully selected to produce idiomatic, readable code.
So, I'd vote for `itself` too:
```ruby
url.itself # return itself
url.itself { |u| open(u).read } # return "itself -> fetch from the network"
```
There are some other good options (listed, for ex., [here](https://bugs.ruby-lang.org/issues/12760#note-5)), that are easy to read, like `apply`, `as`, `chain`, that will produce the code you could read "naturally".
`yield_self` is definitely the ugliest of them. It looks like ruby-core devs saying "we don't think we need this method, but OK, if you ask so frequently... take that!"
----------------------------------------
Feature #13559: Change implementation of Feature #6721
https://bugs.ruby-lang.org/issues/13559#change-64790
* Author: dunrix (Damon Unrix)
* Status: Feedback
* Priority: Normal
* Assignee:
* Target version:
----------------------------------------
Hi,
please reconsider implementation of feature request #6721 planned for Ruby 2.5.0 .
Instead of introducing new method `Object#yield_self`, just reuse existing `Object#itself` by taking an optional block argument.
Find it much clearer and more logical solution, not superfluous polluting of API space.
`Object#itself` just returns target object, optional block would return alternative value with target object passed as block argument.
Prototyped sol. in Ruby:
~~~
class Object
def itself
block_given? ? yield(self) : self
end
end
~~~
Not aware of any case, where it would break backward compatibility.
--
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>