[#62297] Re: [ruby-cvs:52906] nari:r45760 (trunk): * gc.c (gc_after_sweep): suppress unnecessary expanding heap. — Eric Wong <normalperson@...>
[email protected] wrote:
7 messages
2014/05/02
[#62307] Re: [ruby-cvs:52906] nari:r45760 (trunk): * gc.c (gc_after_sweep): suppress unnecessary expanding heap.
— SASADA Koichi <ko1@...>
2014/05/03
(2014/05/03 4:41), Eric Wong wrote:
[#62402] Re: [ruby-cvs:52906] nari:r45760 (trunk): * gc.c (gc_after_sweep): suppress unnecessary expanding heap.
— Eric Wong <normalperson@...>
2014/05/05
SASADA Koichi <[email protected]> wrote:
[#62523] [ruby-trunk - Feature #9632] [PATCH 0/2] speedup IO#close with linked-list from ccan — ko1@...
Issue #9632 has been updated by Koichi Sasada.
3 messages
2014/05/11
[#62556] doxygen (Re: Re: [ruby-trunk - Feature #9632] [PATCH 0/2] speedup IO#close with linked-list from ccan) — Tanaka Akira <akr@...>
2014-05-11 8:50 GMT+09:00 Eric Wong <[email protected]>:
3 messages
2014/05/13
[#62727] [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl — Eric Wong <normalperson@...>
rb_unlink_method_entry may cause old_me to be swept before the new
7 messages
2014/05/24
[#63039] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— SASADA Koichi <ko1@...>
2014/06/10
Hi,
[#63077] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— Eric Wong <normalperson@...>
2014/06/10
SASADA Koichi <[email protected]> wrote:
[#63086] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— SASADA Koichi <ko1@...>
2014/06/11
(2014/06/11 4:47), Eric Wong wrote:
[#63087] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— Eric Wong <normalperson@...>
2014/06/11
SASADA Koichi <[email protected]> wrote:
[#62862] [RFC] README.EXT: document rb_gc_register_mark_object — Eric Wong <normalperson@...>
Any comment on officially supporting this as part of the C API?
5 messages
2014/05/30
[ruby-core:62853] [ruby-trunk - Bug #9883] [Closed] Different behaviour between `==` and hash key lookup regarding multibyte character fragment
From:
nobu@...
Date:
2014-05-30 06:30:58 UTC
List:
ruby-core #62853
Issue #9883 has been updated by Nobuyoshi Nakada.
Description updated
Status changed from Open to Closed
----------------------------------------
Bug #9883: Different behaviour between `=3D=3D` and hash key lookup regardi=
ng multibyte character fragment
https://bugs.ruby-lang.org/issues/9883#change-46972
* Author: Tsuyoshi Sawada
* Status: Closed
* Priority: Normal
* Assignee:=20
* Category:=20
* Target version:=20
* ruby -v: 2.1
* Backport:=20
----------------------------------------
This question is reported in stackoverflow (http://stackoverflow.com/questi=
ons/23946127). When a multibyte character is split by `slice`, `=3D=3D` ign=
ores the split fragment of the character, while key lookup on hash does not:
~~~ruby
s1 =3D "=E2=80=99xxxxxxxxxxxxxxxxxxxxxxxx".slice(1, 24)
s2 =3D "xxxxxxxxxxxxxxxxxxxxxxxx"
s1 =3D=3D s2 # =3D> true
{s2=3D>""}.key?(s1) # =3D> false
~~~
This is inconsistent, and I believe either of the above two is a bug. If it=
is not a bug, but intended, then it is misleading, and I propose the featu=
re should be changed.
--=20
https://bugs.ruby-lang.org/