extendr_engine/lib.rs
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151
//! Embeds a a single R process
//!
//! Using R's C-API requires the embedding of the R runtime.
//! Thus, when using bindings in `libR-sys`, it is necessary that
//! either the a R process is the caller, or that the process instantiates
//! an accompanying R process. Otherwise, a run-time error occurs e.g.
//! `(signal: 11, SIGSEGV: invalid memory reference)` or
//!
//! ```text
//! Caused by:
//! process didn't exit successfully: `/extendr/tests/extendrtest/target/debug/deps/extendrtest-59155c3c146ae614` (signal: 11, SIGSEGV: invalid memory reference)
//! ```
//!
//! ## Testing
//!
//! Within tests, one must use [`test!`] or [`with_r`] as a wrapper around
//! code that uses the R runtime, e.g.
//!
//! ```no_run
//! #[test]
//! fn testing_r_code() {
//! with_r(|| {
//!
//! });
//! }
//! ```
//!
//! Similarly with `test!` that is available in `extendr_api`, one may
//!
//! ```no_run
//! #[test]
//! fn testing_r_code() {
//! test! {
//!
//! };
//! }
//! ```
//!
//! The advantage of `test!` is that it allows the use of `?` in test code, while
//! `with_r` is not macro-based, thus code formatter `rustfmt` and rust LSPs (Rust Analyzer, Rust Rover, etc.)
//! works within `with_r` without any problems.
//!
//!
//! ## Binaries
//!
//! In a binary program, one may use [`start_r`] directly in the `main`-function.
//!
//! There is no `end_r`, as we terminate the R process setup, when the parent
//! process terminates.
//!
//! [`test!`]: https://docs.rs/extendr-api/latest/extendr_api/macro.test.html
//!
// # Internal documentation
//
// ## Background
//
//
// See [Rembedded.c](https://github.com/wch/r-source/blob/trunk/src/unix/Rembedded.c).
//
// [Rinside](https://github.com/eddelbuettel/rinside)
//
//
use libR_sys::*;
use std::os::raw;
use std::sync::Once;
// Generate mutable static strings.
// Much more efficient than `CString`.
// Generates asciiz.
macro_rules! cstr_mut {
($s: expr) => {
concat!($s, "\0").as_ptr() as *mut raw::c_char
};
}
static START_R: Once = Once::new();
pub fn start_r() {
START_R.call_once(|| {
unsafe {
if std::env::var("R_HOME").is_err() {
// env! gets the build-time R_HOME stored by libR-sys
std::env::set_var("R_HOME", env!("R_HOME"));
}
// Due to Rf_initEmbeddedR using __libc_stack_end
// We can't call Rf_initEmbeddedR.
// Instead we must follow rustr's example and call the parts.
//let res = unsafe { Rf_initEmbeddedR(1, args.as_mut_ptr()) };
// NOTE: R will crash if this is called twice in the same process.
Rf_initialize_R(
3,
[cstr_mut!("R"), cstr_mut!("--slave"), cstr_mut!("--no-save")].as_mut_ptr(),
);
// In case you are curious.
// Maybe 8MB is a bit small.
// eprintln!("R_CStackLimit={:016x}", R_CStackLimit);
R_CStackLimit = usize::MAX;
setup_Rmainloop();
}
});
}
/// Close down the R interpreter. Note you won't be able to
/// Restart it, so use with care or not at all.
fn end_r() {
unsafe {
//Rf_endEmbeddedR(0);
R_RunExitFinalizers();
//CleanEd();
R_CleanTempDir();
}
}
/// Ensures that an embedded R instance is present when evaluating
/// `f`.
pub fn with_r(f: impl FnOnce()) {
start_r();
f();
// For compatibility with `test!` in `extendr-api/src/rmacros.rs`, there
// is no `end_r()` call here.
}
#[ctor::dtor]
fn shutdown_r() {
if START_R.is_completed() {
end_r();
}
}
#[cfg(test)]
mod tests {
use super::*;
#[test]
fn test_engine() {
// If this is the first call, it should wake up the interpreter.
start_r();
// This should do nothing.
start_r();
// Ending the interpreter is bad if we are running multiple threads.
// So avoid doing this in tests.
//end_r();
}
}