[][src]Trait artichoke_backend::gc::MrbGarbageCollection

pub trait MrbGarbageCollection {
    fn create_arena_savepoint(
        &mut self
    ) -> Result<ArenaIndex<'_>, ArenaSavepointError>;
fn live_object_count(&mut self) -> i32;
fn mark_value(&mut self, value: &Value);
fn incremental_gc(&mut self);
fn full_gc(&mut self);
fn enable_gc(&mut self) -> State;
fn disable_gc(&mut self) -> State; }

Garbage collection primitives for an mruby interpreter.

Required methods

fn create_arena_savepoint(
    &mut self
) -> Result<ArenaIndex<'_>, ArenaSavepointError>

Create a savepoint in the GC arena.

Savepoints allow mruby to deallocate all of the objects created via the C API.

Normally objects created via the C API are marked as permanently alive ("white" GC color) with a call to mrb_gc_protect.

The returned ArenaIndex implements Drop, so it is sufficient to let it go out of scope to ensure objects are eventually collected.

fn live_object_count(&mut self) -> i32

Retrieve the number of live objects on the interpreter heap.

A live object is reachable via top self, the stack, or the arena.

fn mark_value(&mut self, value: &Value)

Mark a Value as reachable in the mruby garbage collector.

fn incremental_gc(&mut self)

Perform an incremental garbage collection.

An incremental GC is less computationally expensive than a full GC, but does not guarantee that all dead objects will be reaped. You may wish to use an incremental GC if you are operating with an interpreter in a loop.

fn full_gc(&mut self)

Perform a full garbage collection.

A full GC guarantees that all dead objects will be reaped, so it is more expensive than an incremental GC. You may wish to use a full GC if you are memory constrained.

fn enable_gc(&mut self) -> State

Enable garbage collection.

Returns the prior GC enabled state.

fn disable_gc(&mut self) -> State

Disable garbage collection.

Returns the prior GC enabled state.

Loading content...

Implementors

impl MrbGarbageCollection for Artichoke[src]

Loading content...