Issue #7363 has been updated by mame (Yusuke Endoh).

Status changed from Open to Rejected

As drbrain said, this is the convention in Ruby.  There is no reason to hate only Pathname.
Because of compatibility, it is impossible to remove all methods that is named after the corresponding class, i.e., Integer, Array, etc.

-- 
Yusuke Endoh <mame / tsg.ne.jp>
----------------------------------------
Feature #7363: Remove the global Pathname() method
https://bugs.ruby-lang.org/issues/7363#change-33728

Author: aef (Alexander E. Fischer)
Status: Rejected
Priority: Normal
Assignee: 
Category: lib
Target version: 


About a year ago I sumbitted an not yet accepted patch for Ruby on GitHub which deprecates the global Pathname() method and adds the .[] operator to the Pathname class. The patch got ignored, supposedly because I didn't post it here.

https://github.com/ruby/ruby/pull/61

I think poisoning the global namespace with methods named after classes should be considered bad style. Instead, all related methods should lie below the Class' namespace. I hope you share that opinion.

As some User once suggested that probably only collection type classes (e.g. Set) should have a .[] operator, I'm no longer proposing to add .[] instead to Pathname.

If you like the idea, please let me know. I will modify the patch then.


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