From: "NAKAMURA, Hiroshi" <nahi@...>
Date: 2000-07-06T11:13:44+09:00
Subject: [ruby-talk:03851] Re: Array.uniq! returning nil

Hi, matz,

Thank you for your comment.

> From: Yukihiro Matsumoto
> Sent: Thursday, July 06, 2000 12:15 AM

> |http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-dev/9096
> |We Japanese users discussed this issue, but we could not come to
> |a conclusion.  I cannot find any objection now.  Matz, how do you
> |think this proposition?
> 
> Hmm, I thought I (we) came to the negative conclusion.

Hmm.
Accoding Blade's nice looking threading view;
http://blade.nagaokaut.ac.jp/cgi-bin/vframe.rb/ruby/ruby-dev/9052?9024-9551 ,
I cannot find objection to [ruby-dev:9096] and [ruby-dev:9146].
I thought that proposition could be accepted (for me, at least).

> |Aleksi, how do you think 'String#gsub?'.  Seeing 'String#gsub?',
> |how do people think?
> 
> I don't vote for them, if they actually substitute strings.
> Predicates should not have any side effect.

Definitely.

'String#gsub?' should not be defined?

Nishi-san's proposition in [ruby-dev:9096]:
  String#gsub   => create substituted string and returns it.
  String#gsub!  => substitutes itself and returns self
  String#gsub!? => substitutes itself and returns if modification is done or not.
  String#gsub?  => create substituted string and returns if modification is done or not. !?!?