Skip to main content

Crate ring_lang_rs

Crate ring_lang_rs

Expand description

§ring-lang-rs

Rust bindings for the Ring programming language.

§Thread Safety

Ring has no GIL (Global Interpreter Lock). Threading works as follows:

Separate states are independent: Multiple ring_state_new() calls create isolated VMs
Shared state across threads: Use ring_vm_runcodefromthread() which creates a per-thread VM that shares global scope with the main VM. Mutex protection is applied to globals, function hash table, variable hash table, and memory pool during thread creation/deletion.
Memory pool: Thread-safe only after calling ring_vm_mutexfunctions() to register mutex callbacks, and only when using the threading API (ring_vm_runcodefromthread)

§Memory Safety

Most functions in this crate are thin wrappers around Ring’s C API. Callers must ensure:

Pointers (RingState, RingList, RingVM) are valid and non-null
Objects are not used after being deleted
ring_list_getstring_str() returns an owned String (safe to store)
ring_api_getstring_str() returns a reference valid only during the callback

Re-exports§

pub use api::*;
pub use general::*;
pub use item::*;
pub use list::*;
pub use state::*;
pub use string::*;
pub use vm::*;

Modules§

api
ffi
general
item
list
macros
state
string
vm

Macros§

Constants§

Type Aliases§

RingFunc
RingList
RingState
RingVM