[ruby-core:65040] [ruby-trunk - Feature #10177] Hash#has_key? and Hash#has_value? should be deprecated

Issue #10177 has been updated by Yusuke Endoh.


I guess the culture gap (not language gap) is leading to imbroglio in this case.

http://en.wikipedia.org/wiki/High-_and_low-context_cultures

Many Japanese people feel comfortable with "hash.key?(:foo)", because they are in a higher-context culture.

-- 
Yusuke Endoh <[e-mail]>

----------------------------------------
Feature #10177: Hash#has_key? and Hash#has_value? should be deprecated
https://bugs.ruby-lang.org/issues/10177#change-48909

* Author: gogo tanaka
* Status: Open
* Priority: Normal
* Assignee: 
* Category: lib
* Target version: 
----------------------------------------
I referred to this Matz's remark.

http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/43765

And I agree with him, I supposed `Hash#has_key?` should be preferred over `Hash#key?`, 

so I replaced all of `Hash#has_key?` and `Hash#has_value?` in `lib/*` with `Hash#key?` and `Hash#value?` 

---Files--------------------------------
Replace_Hash#has_something.PATCH (20.4 KB)


-- 
https://bugs.ruby-lang.org/