v0.1.11

Fixed:
- Handle the `UNPARKING` state correctly in `Receiver::drop()`. Fixes a panic that could
  occur if a `Receiver` had been first polled as a future and then was being dropped
  in parallel with the `Sender` sending a message.

v0.1.10

Added:
- Add `is_closed` and `has_message` to the `Receiver`. Allows polling for the channel
  state without modifying the channel or pulling the message from it.
- Make the cargo features show up on docs.rs for better discoverability.

v0.1.9

Added:
- Implement `Sync` for `Sender`. There is not a whole lot someone can do with a `&Sender`,
  but this allows storing the sender in places that are overly conservative and require
  a `Sync` bound on the content.

v0.1.8

- Change how loom concurrency testing is triggered. To get rid of `loom` in the dependency tree
  `oneshot` pulls in, it has in addition to being gated behind `cfg(oneshot_loom)` also been made
  an optional dependency. This makes this library way smaller for downstream consumers.
  This has the downside that the crate now exposes a `loom` feature.
  DOWNSTREAM USERS ARE NOT SUPPOSED TO EVER ENABLE THIS. No stability or semver
  guarantees exist around the `loom` feature.
  This change ultimately makes no difference for any user of `oneshot` in regular usage.

* Add `is_closed` method to the `Sender`.