Project

General

Profile

Feature #6557

Make rb_hash_clear() public

Added by Iñaki Baz Castillo almost 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
[ruby-core:45480]

Description

Any reason for rb_hash_clear() not to be public C API?:

static VALUE
rb_hash_clear(VALUE hash)
{
rb_hash_modify_check(hash);
if (!RHASH(hash)->ntbl)
return hash;
if (RHASH(hash)->ntbl->num_entries > 0) {
if (RHASH(hash)->iter_lev > 0)
rb_hash_foreach(hash, clear_i, 0);
else
st_clear(RHASH(hash)->ntbl);
}

return hash;

}

History

#1 [ruby-core:45481] Updated by Iñaki Baz Castillo almost 4 years ago

The same for rb_hash_size().

#2 [ruby-core:45490] Updated by Yui NARUSE almost 4 years ago

  • Status changed from Open to Feedback

ibc (Iñaki Baz Castillo) wrote:

Any reason for rb_hash_clear() not to be public C API?:

Because anyone hadn't request it to be public.
If a function is a public, we can't change the API.
So we don't make it public until anyone request it.

Now you request, could you show the use case of rb_hash_clear() ?

#3 [ruby-core:45491] Updated by Iñaki Baz Castillo almost 4 years ago

Well, I have a C extension (a reactor based on libuv) in which I would like to perform the "loop release" within a single C function (to avoid some steps of the function to be interrupted by an exception or whatever). In such a "release" function I must clear some Ruby arrays and hashes.

Note that rb_ary_clear() is public.

PS: BTW, I don't receive mails when somebody comments or updates an issue reported by me, is it normal? I use Redmine so I'm sure I've properly configured my account in this Redmine.

Thanks a lot.

#4 [ruby-core:50017] Updated by Yusuke Endoh over 3 years ago

  • Status changed from Feedback to Closed

Congrats, rb_hash_clear() was public since r37480.

--
Yusuke Endoh mame@tsg.ne.jp

Also available in: Atom PDF