aboutsummaryrefslogtreecommitdiffstats
path: root/proc.c
diff options
context:
space:
mode:
authorAaron Patterson <tenderlove@ruby-lang.org>2019-08-12 16:09:21 -0400
committerAaron Patterson <tenderlove@ruby-lang.org>2019-08-12 16:44:54 -0400
commitaac4d9d6c7e6b6b0742f3941b574f6006ccb5672 (patch)
treeb1f2906b04075227249ee040111e94a846b99ab2 /proc.c
parent404850e13446c79fb6142f1b32b219753e5cd726 (diff)
downloadruby-aac4d9d6c7e6b6b0742f3941b574f6006ccb5672.tar.gz
Rename rb_gc_mark_no_pin -> rb_gc_mark_movable
Renaming this function. "No pin" leaks some implementation details. We just want users to know that if they mark this object, the reference may move and they'll need to update the reference accordingly.
Diffstat (limited to 'proc.c')
-rw-r--r--proc.c10
1 files changed, 5 insertions, 5 deletions
diff --git a/proc.c b/proc.c
index 2d931e77f0..5957cc3c7b 100644
--- a/proc.c
+++ b/proc.c
@@ -297,7 +297,7 @@ binding_mark(void *ptr)
RUBY_MARK_ENTER("binding");
block_mark(&bind->block);
- rb_gc_mark_no_pin(bind->pathobj);
+ rb_gc_mark_movable(bind->pathobj);
RUBY_MARK_LEAVE("binding");
}
@@ -1363,10 +1363,10 @@ static void
bm_mark(void *ptr)
{
struct METHOD *data = ptr;
- rb_gc_mark_no_pin(data->recv);
- rb_gc_mark_no_pin(data->klass);
- rb_gc_mark_no_pin(data->iclass);
- rb_gc_mark_no_pin((VALUE)data->me);
+ rb_gc_mark_movable(data->recv);
+ rb_gc_mark_movable(data->klass);
+ rb_gc_mark_movable(data->iclass);
+ rb_gc_mark_movable((VALUE)data->me);
}
static void