jni-rs VS mutagen

I do have education and real experience in the field. See, for example, my recent work on the rather arcane subject of Rust↔Java FFI. You don't get to pull rank with me, son. I know quite well what CreateFile does. (Fun fact: it creates a file handle, i.e. opens a file, and may or may not create the file itself.)

I've been playing around with jni-rs, I'm eventually planning on developing an app with Java gui and Rust backend. However I'm having some trouble advancing past HelloWorld lol. For example, here's some simple code that doesn't work and I really can't figure out why:

- JNI - how well does https://github.com/jni-rs/jni-rs work? Assuming that Firefox runs on Android and uses Rust this should be reasonable to work with?

Even so, staying relatively close to the Java focus of the class might be a good idea, since it will help prepare you for the AP exam. One idea would be using jni-rs to build Java bindings for a useful Rust library. Interesting candidates might be io-uring, lockfree, or even pyo3, if you wanted to try your hand at integrating Java and Python.

There are two testing techniques you didn't mention: Snapshot tests (which are greatly simplified using the insta crate and mutation testing (which can be done on nightly with my mutagen crate.

How does this compare to mutagen?

Do you mean as part of build.rs? Yes, that's certainly doable, and has been done in the past. You can use env!("OUT_DIR") for that. Examples you may want to refer to include my mutagen crate and criterion.

Would be great if this could include mutation testing.

I wrote a good number of macros though, both macro_rules! and various proc_macros. The latest iteration of overflower has both, for example. mutagen is a mutation testing tool built as a proc macro, and it's helper library has a bunch of macros, too. compact_arena uses macros to tie unique lifetime tags to arenas.

Also there are far more mutation testing frameworks. I maintain the rust-based mutagen one. There are also LLVM-based ones (etc. mull) that can cover multiple languages (but may yield mutations not expressible in your preferred one).

Cargo (and Rust) makes it so easy to write test cases that you should really use it to find these kinds of bugs. And there are other good test crates available: mutagen, quickcheck, etc.

I had a student completely reachitecture my mutagen tool, and saw some working on various clippy contributions.