Issue #6381 has been updated by drbrain (Eric Hodel).

Status changed from Assigned to Third Party's Issue

=begin
Documentation for Module.included is displayed by using ri generated from 1.9.3:

  $ ~/.multiruby/install/1.9.3-p125/bin/ri Module.included
  Module.included
  
  (from ruby core)

So the display of documentation for Module.included is not an issue of ruby.

I added directives to pick up documentation for private_constant and public_constant for trunk:

  $ ri Module.public_constant
  Nothing known about Module.public_constant
  $ ri --no-standard -d .ext/rdoc/ Module.public_constant
  Module.public_constant
  
  (from .../ruby/trunk/.ext/rdoc)

I have no control over how documentation is generated for uses beyond the built-in ri data such as http://ruby-doc.org, so I will close this as a "third party issue".  You should follow up with the contact email at the bottom of http://ruby-doc.org: suggestions / ruby-doc.org

=end

----------------------------------------
Bug #6381: Useful methods like included don't appear in RDoc
https://bugs.ruby-lang.org/issues/6381#change-26515

Author: agrimm (Andrew Grimm)
Status: Third Party's Issue
Priority: Normal
Assignee: drbrain (Eric Hodel)
Category: 
Target version: 
ruby -v: ruby 1.9.1p378 (2010-01-10 revision 26273) [i386-mingw32]


=begin
Methods like (({Module.included})) and (({Module.private_constant})) don't appear in ruby-doc.org's documentation, because they are private methods. This can cause difficulty for new users of Ruby, for example in http://stackoverflow.com/q/10369876/38765

While there is a rationale behind not showing some private methods, because they are implementation details that should not be relied upon by users of Ruby, this isn't the case here.

This issue has been discussed in ruby-core:40662 and elsewhere, but is something that needs to be put in a bug tracker.
=end



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