[#71439] [Ruby trunk - Feature #11339] [PATCH] io.c: avoid kwarg parsing in C API — matz@...
Issue #11339 has been updated by Yukihiro Matsumoto.
7 messages
2015/11/11
[#71473] Re: [Ruby trunk - Feature #11339] [PATCH] io.c: avoid kwarg parsing in C API
— Eric Wong <normalperson@...>
2015/11/13
Entire series for sockets
[#71450] Ruby 2.3.0-preview1 Released — "NARUSE, Yui" <naruse@...>
Hi,
5 messages
2015/11/11
[#71617] [Ruby trunk - Feature #11664] [PATCH] introduce rb_autoload_value to replace rb_autoload — nobu@...
Issue #11664 has been updated by Nobuyoshi Nakada.
3 messages
2015/11/20
[#71721] [Ruby trunk - Feature #11741] Migrate Ruby to Git from Subversion — me@...
Issue #11741 has been updated by Jon Moss.
4 messages
2015/11/28
[ruby-core:71456] [Ruby trunk - Feature #8237] [Closed] Logical method chaining via inferred receiver
From:
shibata.hiroshi@...
Date:
2015-11-12 01:16:18 UTC
List:
ruby-core #71456
Issue #8237 has been updated by Hiroshi SHIBATA.
Status changed from Open to Closed
this feature is supported at #11537
----------------------------------------
Feature #8237: Logical method chaining via inferred receiver
https://bugs.ruby-lang.org/issues/8237#change-54826
* Author: Tom Wardrop
* Status: Closed
* Priority: Normal
* Assignee:
----------------------------------------
=begin
This is a feature suggestion that was raised while discussing issue #8191. The feature suggestion is to introduce some form of logical method chaining to address this reasonably common pattern:
user && user.profile && user.profile.website && user.profile.website.thumbnail
It would be reasonably trivial to shorten this to:
user && .profile && .website && .thumbnail
The implementation I propose would be for Ruby to allow an inferred receiver; the dot prefix would be the syntax for this. The inferred receiver would resolve to the result of the last expression in the current scope. For illustrative purposes, the following would work under this proposal:
"some string"
puts .upcase #=> SOME STRING
Another example:
puts .upcase if obj.success_message || obj.error_message
# Instead of...
message = (obj.success_message || obj.error_message)
puts message.upcase if message
This can also potentially provide an alternative option in syntactically awkward scenario's, such as dealing with the return value of an if statement or a catch block, avoiding the need for temporary variable assignment:
catch :halt do
# Do something
end
if .nil?
log.info "Request was halted"
response.body = "Sorry, but your request could not be completed"
end
The logical chaining scenario is the main use case however. I just wanted to demonstrate how the proposed implementation could also be used in other creative ways.
=end
--
https://bugs.ruby-lang.org/