You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
token_stream and skip_document inconsistency #1492
Complex#conjugate have token_stream but marked as skip_document
Complex#conjugate has ▶︎Source toggle but description is skipped. Complex#conj has document but ▶︎Source is not available.
The behavior of this bug looks similar to #1335 but the cause is different.
skip_description
# Whether to skip the method description, true for methods that have
# aliases with a call-seq that doesn't include the method name.
I think this design decision makes sense. There is a room for discussion whether we really need to generate duplicated document for the same method.
token_stream
Among method/aliases with the same source, RDoc seems to select one main method. token_stream is associated to that method object.
RDoc shouldn't select description-skipped method object as main method.
Hi @tompng. I started looking into this and wanted to confirm: is this considered a bug, or is this the intended behavior in RDoc? If it's the latter, would updating the call-seqs for those methods to match the current behavior be the preferred approach? If this isn't already documented, we could also clarify it in the documentation. This does appear to be a bug.
Activity
extern-c commentedon Feb 28, 2026
Hi @tompng. I started looking into this and wanted to confirm: is this considered a bug, or is this the intended behavior in RDoc? If it's the latter, would updating the call-seqs for those methods to match the current behavior be the preferred approach? If this isn't already documented, we could also clarify it in the documentation.This does appear to be a bug.