From 63fe03aa4e9bba62dec83e5b7927c47b9599eeff Mon Sep 17 00:00:00 2001
From: Peter Zhu <peter@peterzhu.ca>
Date: Tue, 20 Dec 2022 15:09:14 -0500
Subject: [PATCH] [DOC] Fix call-seq for GC methods

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.
---
 gc.c  | 2 +-
 gc.rb | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/gc.c b/gc.c
index 977a2966f7..62fbc6ff72 100644
--- a/gc.c
+++ b/gc.c
@@ -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.
  *
diff --git a/gc.rb b/gc.rb
index 2fbef475e0..3912d35f4c 100644
--- a/gc.rb
+++ b/gc.rb
@@ -219,7 +219,7 @@ module GC
   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
   #