I'm against this because it will be abused, and cause chaos vis-a-vis well-established conventions in the Ruby world. The example given in the ticket, defining

I'm against this because it will be abused, and cause chaos vis-a-vis well-established conventions in the Ruby world. The example given in the ticket, defining a global constant PORT in the root namespace and then loading it separately into two apps--nobody actually does in Ruby this today, because it is well-known that it will cause conflicts. Any gem (Ruby library) that did this sort of thing has long-since been barked at and corrected--the solution is simply to nest the constant inside your main module e.g. MyGem::PORT. Now, gems will be free to define whatever constants/modules/etc. they want. When someone files an issue, the response can be: "Oh you don't like that I redefined Array? Load my gem in a namespace!"