RDoc needs a directive to not clobber an overridden method definition's documentation, but add to it.
Use case: I wanted to find out how require worked.
Unfortunately, in RDoc-generated documentation, all I could find is information on how by requiring rubygems the behavior of Kernel.require changed, but nothing about its original behavior.
If RDoc had a directive to add, don't replace documentation, and it was used on the rubygems' monkeypatch of Kernel.require, the original documentation wouldn't have gotten lost.
RDoc needs a directive to not clobber an overridden method definition's documentation, but add to it.
Use case: I wanted to find out how
requireworked.Unfortunately, in RDoc-generated documentation, all I could find is information on how by requiring
rubygemsthe behavior ofKernel.requirechanged, but nothing about its original behavior.If RDoc had a directive to add, don't replace documentation, and it was used on the rubygems' monkeypatch of
Kernel.require, the original documentation wouldn't have gotten lost.