You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Heya, I just wanted to make sure to give a heads up here that I've been chipping away at some maintenance chores for jni-sys and based on issues I've seen while working on the jni crate I was planning a few semver breaking changes.
The latter change in particular may invole some boilerplate changes here but at least as far as the jni crate goes I'm glad I looked at this this since it has highlighted several places where the jni crate was using > 1.1 functions without checking the version at runtime.
The text was updated successfully, but these errors were encountered:
Heya, I just wanted to make sure to give a heads up here that I've been chipping away at some maintenance chores for jni-sys and based on issues I've seen while working on the
jni
crate I was planning a few semver breaking changes.It'd be good if you can take a look at the 'Release 0.4' milestone here: https://github.com/jni-rs/jni-sys/milestone/1
The two notable changes are:
jboolean
an alias forbool
: ref Considering redefiningjboolean
as either anbool
or our own#[repr(u8)]
enum jni-rs/jni-sys#19, Add Array wrapper types with lifetimes jni-rs/jni-rs#400 (comment) and Makejboolean
an alias forbool
instead ofu8
jni-rs/jni-sys#23JNINativeInterface
+JNIInvokeInterface_
into unions that namespace function pointers by the JNI version they were added (and remove the misleadingOption
wrappers), ref: Turn JNINativeInterface + JNIInvokeInterface_ into unions jni-rs/jni-sys#28 and Removes the Options around the function pointers jni-rs/jni-sys#25The latter change in particular may invole some boilerplate changes here but at least as far as the
jni
crate goes I'm glad I looked at this this since it has highlighted several places where thejni
crate was using > 1.1 functions without checking the version at runtime.The text was updated successfully, but these errors were encountered: