wuwbobo2021

(my previous wrong comments written in this post are deleted by myself. It's about my mistake of testing the #555 draft version without switching to the right branch after `git...

> ... you're responsible for guaranteeing that you aren't materializing a `JNIEnv` while you already have some other mutable `JNIEnv` in scope. I don't currently see how that constraint can...

> (in the current design) ... the way we then guarantee that new local references will get associated with the correct `JNIEnv` lifetime (in case you can still see an...

> I can't think of any JNIEnv APIs that would make sense for interacting with an outer env via a shared reference compared to just using the closer mutable reference...

Sorry, I don’t understand what is “classic”. It’s merely counting statically for groups of stones that may extend to length 5 in the future. You can check the function marked...

这个设想是有严重缺陷还是毫无意义? 请指教。

You don't have to choose `btleplug` which is originally a support crate for the authors money maker `buttplug`. There are some other alternatives like `bluest`, you can add support for...

> The unqualified segments can be glued back together to make the string, right? I've already tried to do it, but it's not an ideal solution: it constructs a new...

Sorry, I think it's not easy to make the change: parsed fields available in `ClassFile` do use the borrowed class data, but the original class data isn't available as a...

I'm about to finish porting `java-spaghetti` to `cafebabe` with some workarounds, but I can't make previous unit tests like `method_mangling_style_mangle_test` working, because functions like `parse_method_descriptor` aren't exposed by `cafebabe`. I'll...