Skip to content

Commit

Permalink
[DOC] Fix call-seq for GC methods
Browse files Browse the repository at this point in the history
RDoc parses the last arrow in the call-seq as the arrow for the return
type. It was getting confused over the arrow in the hash.
  • Loading branch information
peterzhu2118 committed Dec 20, 2022
1 parent 790b3f7 commit 63fe03a
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion gc.c
Expand Up @@ -10796,7 +10796,7 @@ gc_update_references(rb_objspace_t *objspace)
#if GC_CAN_COMPILE_COMPACTION
/*
* call-seq:
* GC.latest_compact_info -> {:considered=>{:T_CLASS=>11}, :moved=>{:T_CLASS=>11}}
* GC.latest_compact_info -> hash
*
* Returns information about object moved in the most recent GC compaction.
*
Expand Down
2 changes: 1 addition & 1 deletion gc.rb
Expand Up @@ -219,7 +219,7 @@ def self.stat_heap heap_name = nil, hash_or_key = nil
end

# call-seq:
# GC.latest_gc_info -> {:gc_by=>:newobj}
# GC.latest_gc_info -> hash
# GC.latest_gc_info(hash) -> hash
# GC.latest_gc_info(:major_by) -> :malloc
#
Expand Down

0 comments on commit 63fe03a

Please sign in to comment.