…ritten

If writes to the BzDecoder end before it has been fed the entire stream
and the output buffer has already been flushed to the wrapped writer,
then the Drop implementation will loop forever. On drop, try_finish() is
called, which repeatedly tries to write() until BZ_STREAM_END is
returned or an error occurs, but neither scenario happens if there's no
input nor output data to process.

This commit makes try_finish() return an UnexpectedEof error in this
scenario.

Signed-off-by: Andrew Gunnerson <accounts+github@chiller3.com>

…itional input

Co-authored-by: bjorn3 <17426603+bjorn3@users.noreply.github.com>

libc does not expose those types for some targets (notable wasm32-unknown-unknown)

This ensures that finish will always be attempted to be called, for
example when operating as a `Box<dyn Writer>`.

…regress

Without the `impl<W: Write> Drop for BzEncoder<W>` the test fails with
the error message:
    called `Result::unwrap()` on an `Err` value: Custom { kind: UnexpectedEof, error: "Input EOF reached before logical stream end" }

als use a bit less memory; it's not really needed to prove the point

Updates the requirements on [rand](https://github.com/rust-random/rand) to permit the latest version.
- [Release notes](https://github.com/rust-random/rand/releases)
- [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md)
- [Commits](rust-random/rand@0.8.0...0.9.0)

---
updated-dependencies:
- dependency-name: rand
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

* Disable bzip2-sys build script if rust backend is enabled

Currently if one is to enable rust backend without disabling
default features, the bzip2-sys build script would build the
bzip2 again, making it meaningless to enable the feature.

In many cases disabling default-features is hard (breaking
backwards compatibility), so it'd be better to disable the
bzip2-sys bulid-script, if the rust backend is enabled'

It would still pull in cc-rs and pkg-config, but at least
it won't compile the bzip2 c code again.'

Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>

* Disable bzip2-sys build script if rust backend is enabled

Currently if one is to enable rust backend without disabling
default features, the bzip2-sys build script would build the
bzip2 again, making it meaningless to enable the feature.

In many cases disabling default-features is hard (breaking
backwards compatibility), so it'd be better to disable the
bzip2-sys bulid-script, if the rust backend is enabled'

It would still pull in cc-rs and pkg-config, but at least
it won't compile the bzip2 c code again.'

Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>

* Disable bzip2-sys build script if rust backend is enabled

Currently if one is to enable rust backend without disabling
default features, the bzip2-sys build script would build the
bzip2 again, making it meaningless to enable the feature.

In many cases disabling default-features is hard (breaking
backwards compatibility), so it'd be better to disable the
bzip2-sys bulid-script, if the rust backend is enabled'

It would still pull in cc-rs and pkg-config, but at least
it won't compile the bzip2 c code again.'

Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>

---------

Signed-off-by: Jiahao XU <Jiahao_XU@outlook.com>

Co-authored-by: bjorn3 <17426603+bjorn3@users.noreply.github.com>