Ryuta Kamizono 8afdfdcfc9 Refactor ActiveSupport::Deprecation.deprecate_methods not to expose internal methods ... In #33325, `deprecate_methods` is replaced from `prepend` to completely emurated `alias_method_chain`, it exposed two internal methods `xxx_with_deprecation` and `xxx_without_deprecation`. After that, #34648 restored the `prepend` implementation, which doesn't expose any internal methods, so we no longer be able to ensure to always expose that internal methods. As I said at https://github.com/rails/rails/pull/33325#issuecomment-409016725, I think that internal methods exposed is not a specification but a limitation when using `alias_method_chain`, there is no longer a reason to follow that limitation.		2019-04-19 22:00:09 +09:00
..
behaviors.rb	Change the empty block style to have space inside of the block	2018-09-25 13:19:35 -04:00
constant_accessor.rb	Formatting fix for example code	2017-11-28 18:17:18 -05:00
instance_delegator.rb	[Active Support] require_relative => require	2017-10-21 22:48:27 +09:00
method_wrappers.rb	Refactor ActiveSupport::Deprecation.deprecate_methods not to expose internal methods	2019-04-19 22:00:09 +09:00
proxy_wrappers.rb	Remove unused require "active_support/core_ext/regexp"	2018-07-29 14:51:00 +09:00
reporting.rb	Return back "/" to the end of RAILS_GEM_ROOT	2018-04-20 01:24:46 +03:00