[#71815] [Ruby trunk - Bug #11768] [Open] Add a polymorphic inline cache — tenderlove@...
Issue #11768 has been reported by Aaron Patterson.
6 messages
2015/12/03
[#71819] Re: [Ruby trunk - Bug #11768] [Open] Add a polymorphic inline cache
— Eric Wong <normalperson@...>
2015/12/03
[email protected] wrote:
[#71821] Re: [Ruby trunk - Bug #11768] [Open] Add a polymorphic inline cache
— Aaron Patterson <tenderlove@...>
2015/12/03
On Thu, Dec 03, 2015 at 10:51:08PM +0000, Eric Wong wrote:
[#71824] Re: [Ruby trunk - Bug #11768] [Open] Add a polymorphic inline cache
— Eric Wong <normalperson@...>
2015/12/04
Aaron Patterson <[email protected]> wrote:
[#71818] [Ruby trunk - Feature #11769] [Open] optimize case / when for `nil` — tenderlove@...
Issue #11769 has been reported by Aaron Patterson.
4 messages
2015/12/03
[#71825] Re: [Ruby trunk - Feature #11769] [Open] optimize case / when for `nil`
— Eric Wong <normalperson@...>
2015/12/04
[email protected] wrote:
[#71931] [Ruby trunk - Feature #11786] [Open] [PATCH] micro-optimize case dispatch even harder — normalperson@...
Issue #11786 has been reported by Eric Wong.
9 messages
2015/12/08
[#71932] Re: [Ruby trunk - Feature #11786] [Open] [PATCH] micro-optimize case dispatch even harder
— Eric Wong <normalperson@...>
2015/12/08
Oops, I forgot to free the table when iseq is destroyed :x
[#71934] Re: [Ruby trunk - Feature #11786] [Open] [PATCH] micro-optimize case dispatch even harder
— SASADA Koichi <ko1@...>
2015/12/08
On 2015/12/08 12:43, Eric Wong wrote:
[#71936] Re: [Ruby trunk - Feature #11786] [Open] [PATCH] micro-optimize case dispatch even harder
— Eric Wong <normalperson@...>
2015/12/08
SASADA Koichi <[email protected]> wrote:
[#71938] Re: [Ruby trunk - Feature #11786] [Open] [PATCH] micro-optimize case dispatch even harder
— SASADA Koichi <ko1@...>
2015/12/08
On 2015/12/08 13:53, Eric Wong wrote:
[#72028] [Ruby trunk - Feature #11405] [Assigned] [PATCH] hash.c: minor speedups to int/fixnum keys — mame@...
Issue #11405 has been updated by Yusuke Endoh.
5 messages
2015/12/10
[#72040] Re: [Ruby trunk - Feature #11405] [Assigned] [PATCH] hash.c: minor speedups to int/fixnum keys
— Eric Wong <normalperson@...>
2015/12/10
[email protected] wrote:
[#72045] Ruby 2.3.0-preview2 Released — "NARUSE, Yui" <naruse@...>
We are pleased to announce the release of Ruby 2.3.0-preview2.
10 messages
2015/12/11
[#72047] Re: Ruby 2.3.0-preview2 Released
— SASADA Koichi <ko1@...>
2015/12/11
Please add your optimizations before RC1.
[#72054] Re: Ruby 2.3.0-preview2 Released
— Eric Wong <normalperson@...>
2015/12/11
SASADA Koichi <[email protected]> wrote:
[#72436] Re: Ruby 2.3.0-preview2 Released
— SASADA Koichi <ko1@...>
2015/12/22
On 2015/12/11 18:06, Eric Wong wrote:
[#72440] Re: Ruby 2.3.0-preview2 Released
— Eric Wong <normalperson@...>
2015/12/22
SASADA Koichi <[email protected]> wrote:
[#72069] [Ruby trunk - Feature #11405] [PATCH] hash.c: minor speedups to int/fixnum keys — mame@...
Issue #11405 has been updated by Yusuke Endoh.
3 messages
2015/12/12
[#72115] Re: [ruby-cvs:60264] duerst:r53112 (trunk): * enc/ebcdic.h: new dummy encoding EBCDIC-US — "U.NAKAMURA" <usa@...>
Hi,
7 messages
2015/12/14
[#72124] Re: [ruby-cvs:60264] duerst:r53112 (trunk): * enc/ebcdic.h: new dummy encoding EBCDIC-US
— Martin J. Dürst <duerst@...>
2015/12/14
On 2015/12/14 22:34, U.NAKAMURA wrote:
[#72125] Re: [ruby-cvs:60264] duerst:r53112 (trunk): * enc/ebcdic.h: new dummy encoding EBCDIC-US
— "U.NAKAMURA" <usa@...>
2015/12/15
Hi,
[ruby-core:72118] [Ruby trunk - Bug #11816] Partial safe navigation operator
From:
ruby-core@...
Date:
2015-12-14 18:30:48 UTC
List:
ruby-core #72118
Issue #11816 has been updated by Marc-Andre Lafortune.
BTW, this came up in Matt Larraz's PR https://github.com/ruby/ruby/pull/1142
Both Hiroshi Shibata and Benoit Daloze thought (as I did) that `e_error_bytes&.dup.force_encoding(...)` should work.
----------------------------------------
Bug #11816: Partial safe navigation operator
https://bugs.ruby-lang.org/issues/11816#change-55535
* Author: Marc-Andre Lafortune
* Status: Open
* Priority: Normal
* Assignee: Yukihiro Matsumoto
* ruby -v: preview 2
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
I'm extremely surprised (and disappointed) that, currently:
x = nil
x&.foo.bar # => NoMethodError: undefined method `bar' for nil:NilClass
To make it safe, you have to write `x&.foo&.bar`. But if `foo` is never supposed to return `nil`, then that code isn't "fail early" in case it actually does. `nil&.foo.bar` is more expressive, simpler and is perfect if you want to an error if `foo` returned `nil`. To actually get what you want, you have to resort using the old form `x && x.foo.bar`...
In CoffeeScript, you can write `x()?.foo.bar` and it will work well, since it gets compiled to
if ((_ref = x()) != null) {
_ref.foo.bar;
}
All the discussion in #11537 focuses on `x&.foo&.bar`, so I have to ask:
Matz, what is your understanding of `x&.foo.bar`?
I feel the current implementation is not useful and should be changed to what I had in mind. I can't see any legitimate use of `x&.foo.bar` currently.
--
https://bugs.ruby-lang.org/