Fix concerns

This commit is contained in:
Pierre Krieger 2017-12-07 12:34:12 +01:00
parent 4fa9146489
commit f4ba9ddb6d
2 changed files with 8 additions and 8 deletions

View File

@ -16,7 +16,7 @@ and `Clone` traits.
The `JsonFileDatastore::new` method will attempt to load existing data from the path you pass The `JsonFileDatastore::new` method will attempt to load existing data from the path you pass
as parameter. This path is also where the data will be stored. The content of the store is as parameter. This path is also where the data will be stored. The content of the store is
flushed on destruction or if you call `flush()`. flushed on drop or if you call `flush()`.
```rust ```rust
use datastore::Datastore; use datastore::Datastore;
@ -37,9 +37,9 @@ a way to perform queries on the key-value storage, using the `query` method.
The struct returned by the `query` method implements the `Stream` trait from `futures`, The struct returned by the `query` method implements the `Stream` trait from `futures`,
meaning that the result is asynchronous. meaning that the result is asynchronous.
> **Note**: For now the `get` and `has` methods are theoretically blocking, but the only > **Note**: For now the API of the `get` and `has` methods makes them potentially blocking
> available implementation doesn't do any I/O. Maybe these methods will be made > operations, though the only available implementation doesn't block. The API of these
> asynchronous in the future, if deemed necessary. > methods may become asynchronous in the future if deemed necessary.
```rust ```rust
extern crate datastore; extern crate datastore;

View File

@ -39,7 +39,7 @@
//! //!
//! The `JsonFileDatastore::new` method will attempt to load existing data from the path you pass //! The `JsonFileDatastore::new` method will attempt to load existing data from the path you pass
//! as parameter. This path is also where the data will be stored. The content of the store is //! as parameter. This path is also where the data will be stored. The content of the store is
//! flushed on destruction or if you call `flush()`. //! flushed on drop or if you call `flush()`.
//! //!
//! ```no_run //! ```no_run
//! use datastore::Datastore; //! use datastore::Datastore;
@ -60,9 +60,9 @@
//! The struct returned by the `query` method implements the `Stream` trait from `futures`, //! The struct returned by the `query` method implements the `Stream` trait from `futures`,
//! meaning that the result is asynchronous. //! meaning that the result is asynchronous.
//! //!
//! > **Note**: For now the `get` and `has` methods are theoretically blocking, but the only //! > **Note**: For now the API of the `get` and `has` methods makes them potentially blocking
//! > available implementation doesn't do any I/O. Maybe these methods will be made //! > operations, though the only available implementation doesn't block. The API of these
//! > asynchronous in the future, if deemed necessary. //! > methods may become asynchronous in the future if deemed necessary.
//! //!
//! ```no_run //! ```no_run
//! extern crate datastore; //! extern crate datastore;