Marijn Suijten

> @MarijnS95 I didn't find any information about a "minimum error code integer" or "maximum buffer index". The "1000" cut point was completely arbitrary on my side. Anything we can...

Otherwise can you inquire about this over at https://github.com/android/ndk?

> Not a good idea to me, it might break in a new API level. It is already broken by design unless there's a maximum buffer index.

If there are no downsides to `--fastdeploy` that's a welcome flag to add by default. Disabling compression on the other hand sounds like something that's useful in debug scenarios only,...

@agrande Would you mind if I respin the `-0 ""` change, wrapped in debug conditionals? I'm starting to work more with `cargo-apk` and larger libraries, and compression of even relatively...

Thanks @agrande! I've gone ahead and submitted the `-0` change in #283. Unfortunately `--fastdeploy` isn't working on all my dev devices, some are bailing out with `incremental-install` being disallowed/disabled, and...

With the compression disablement squared away I'll do some profiling on my project to see how big the gains are for `--fastdeploy`, and see if we can make an educated...

We can - should - probably enlarge the deprecation notice, perhaps even delete the rest of the README and point readers to a commit prior to removal if they want...

Side-note: it doesn't seem like I have the necessary rights to temporarily un-archive that repo and make the desired change. One of the other maintainers will have to do so.

> Either way, there probably should be an obvious link to the cargo-apk folder How about adding a little "usage" section ~above~/below the "hello world" section, pointing to the various...