From: "kyledecot (Kyle Decot)" <kyle.decot@...>
Date: 2013-06-04T02:43:06+09:00
Subject: [ruby-core:55279] [ruby-trunk - Feature #8462] Module.remove_const inconsistant naming


Issue #8462 has been updated by kyledecot (Kyle Decot).


I understand that it's a dangerous operation but how does naming it inconsistently make any less so? The fact that it's a private method I would think should be protection enough from accidental usage. Naming it inconsistently only serves to make it difficult to find in the documentation.  

matz (Yukihiro Matsumoto) wrote:
> remove is a dangerous operation, thus named inconsistent, as remove_instance_variable etc.
> 
> Matz.


----------------------------------------
Feature #8462: Module.remove_const inconsistant naming
https://bugs.ruby-lang.org/issues/8462#change-39677

Author: kyledecot (Kyle Decot)
Status: Rejected
Priority: Normal
Assignee: 
Category: core
Target version: 


The Module class in Ruby has several methods for dealing w/ constants:

const_set
const_get
const_defined?
const_missing
remove_const 

The last of which is inconsistently named. I propose that we deprecate this method and create a new one called const_unset (as it's the counterpart to const_set).


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