fluencelabs/rust-libp2p
1
0
Fork 0
mirror of https://github.com/fluencelabs/rust-libp2p synced 2025-05-20 22:51:20 +00:00
Code Issues Projects Releases Wiki Activity

Fix concerns

Browse Source
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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
datastore/README.md
View File

@ -16,7 +16,7 @@ and `Clone` traits.
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
flushed on destruction or if you call `flush()`.
flushed on drop or if you call `flush()`.
```rust
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`,
meaning that the result is asynchronous.
> **Note**: For now the `get` and `has` methods are theoretically blocking, but the only
> available implementation doesn't do any I/O. Maybe these methods will be made
> asynchronous in the future, if deemed necessary.
> **Note**: For now the API of the `get` and `has` methods makes them potentially blocking
> operations, though the only available implementation doesn't block. The API of these
> methods may become asynchronous in the future if deemed necessary.
```rust
extern crate datastore;

8
datastore/src/lib.rs
View File

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