[#41916] Proposal: Bitmap Marking GC — Narihiro Nakamura <authornari@...>

Hi.

18 messages 2012/01/05

[#41941] [ruby-trunk - Bug #5851][Open] make check fails when compiling with GCC 4.7 - *** longjmp causes uninitialized stack frame *** — Vit Ondruch <v.ondruch@...>

12 messages 2012/01/06

[#41979] [ruby-trunk - Bug #5865][Open] Exception#== should return false if the classes differ — Hiro Asari <asari.ruby@...>

10 messages 2012/01/08

[#42003] [ruby-trunk - Bug #5871][Open] regexp \W matches some word characters when inside a case-insensitive character class — Gareth Adams <gareth@...>

14 messages 2012/01/09

[#42016] [ruby-trunk - Feature #5873][Open] Adopt FFI over DL — Heesob Park <phasis@...>

15 messages 2012/01/10

[#42149] [ruby-trunk - Feature #5899][Open] chaining comparsions. — Ondrej Bilka <neleai@...>

12 messages 2012/01/16

[#42164] [ruby-trunk - Feature #5903][Open] Optimize st_table (take 2) — Yura Sokolov <funny.falcon@...>

18 messages 2012/01/17

[ruby-core:42273] Re: Fwd: RCR String#{last, first}

From: Rodrigo Rosenfeld Rosas <rr.rosas@...>
Date: 2012-01-30 18:07:21 UTC
List: ruby-core #42273
Em 30-01-2012 14:27, Roger Pack escreveu:
>>> and related
>>> String#first(n)
>>>
>>> Feedback welcome.  If none I'll file it on redmine with a patch.
>>> -roger-
>> I like the idea. I'm just not sure if 'last' would be clear enough...
>> Don't have another suggestion for now, sorry...
> Hmm.  I was thinking "first" and "last" would be good since they would
> match Array#last and Array#first but maybe something like first_chars
> or something?

I find first_chars and last_chars much more readable. But that is my 
personal opinion, feel free to check with others too.

In This Thread