Including the env allows for the convenient execution of methods without having to individually pass the env as an argument to each and every one. Since this is limited to the current thread/stack, these cannot be sanely stored in any kind of static storage, nor shared between threads - instead use a Global if you need to do either.
Will DeleteLocalRef when dropped, invalidating the jobject but ensuring threads that rarely or never return to Java may run without being guaranteed to eventually exhaust their local reference limit. If this is not desired, convert to a plain Ref with:
let local = Local::leak(local);
Not FFI Safe: #[repr(rust)], and exact layout is likely to change - depending on exact features used - in the future. Specifically, on Android, since we're guaranteed to only have a single ambient VM, we can likely store the *const JNIEnv in thread local storage instead of lugging it around in every Local. Of course, there's no guarantee that's actually an optimization...
pub unsafe fn from_env_object(env: *const JNIEnv, object: jobject) -> Self[src]
impl<'env, Class> RefUnwindSafe for Local<'env, Class> where
impl<'env, Class> UnwindSafe for Local<'env, Class> where
type Error = Infallible
The type returned in the event of a conversion error.