Skip to content

Commit

Permalink
Merge pull request #66 from Metaswitch/release-0.15.0
Browse files Browse the repository at this point in the history
Update README and CHANGELOG for 0.15.0.
  • Loading branch information
kw217 committed Jan 28, 2020
2 parents cef8b17 + d5ac6e2 commit 62b1fbf
Show file tree
Hide file tree
Showing 2 changed files with 13 additions and 3 deletions.
6 changes: 3 additions & 3 deletions CHANGELOG.md
Expand Up @@ -11,13 +11,13 @@ version number is tracked in the file `VERSION`.
### Changed
### Fixed

## [0.15.0] - 2020-01-??
## [0.15.0] - 2020-01-28
### Changed
- Drops support for futures 0.1, and implements `std::future` instead, allowing
- Drop support for futures 0.1, and implement `std::future` instead, allowing
you to use this this library inside `async` functions, allowing anything that
returns a `CassFuture` to be `await`ed. This is a breaking change, and will
require you to update your call-sites to either use `std::future`, or wrap
them with a compatibility shim.
them with a compatibility shim (e.g., `futures::compat`).

### Added
- Adds a new method, `Cluster.connect_async` that returns a future, allowing
Expand Down
10 changes: 10 additions & 0 deletions README.md
Expand Up @@ -44,6 +44,16 @@ There are additional examples included with the project in [`tests`](tests/) and
[`examples`](examples/).


## Futures (version 0.15)

Since version 0.15, this crate uses `std::future`, allowing your code to
use `futures:0.3`, `async/await`, etc.

Previous versions (up to 0.14) used `futures:0.1`. You can either remain on
the 0.14 stream, update your code to use `std::future`, or use a compatibility
shim (e.g., `futures::compat`).


## Migrating from version 0.8

The API changed significantly in version 0.10.
Expand Down

0 comments on commit 62b1fbf

Please sign in to comment.