@@ -36,18 +36,18 @@ This crate is available on [crates.io](https://crates.io/crates/bson). To use it
36
36
37
37
``` toml
38
38
[dependencies ]
39
- bson = " 2.0.0-beta.3 "
39
+ bson = " 2.0.0"
40
40
```
41
41
42
42
Note that if you are using ` bson ` through the ` mongodb ` crate, you do not need to specify it in your
43
43
` Cargo.toml ` , since the ` mongodb ` crate already re-exports it.
44
44
45
45
#### Feature Flags
46
46
47
- | Feature | Description | Extra dependencies | Default |
48
- | :-------------| :----------------------------------------------------------------------------------------------- | :-------------------| :--------|
49
- | ` chrono-0_4 ` | Enable support for v0.4 of the [ ` chrono ` ] ( docs.rs/chrono/0.4 ) crate in the public API. | n/a | no |
50
- | ` uuid-0_8 ` | Enable support for v0.8 of the [ ` uuid ` ] ( docs.rs/uuid/0.8 ) crate in the public API. | ` uuid ` 0.8 | no |
47
+ | Feature | Description | Extra dependencies | Default |
48
+ | :-------------| :---------------------------------------------------------------------------------------| :-------------------| :--------|
49
+ | ` chrono-0_4 ` | Enable support for v0.4 of the [ ` chrono ` ] ( docs.rs/chrono/0.4 ) crate in the public API. | n/a | no |
50
+ | ` uuid-0_8 ` | Enable support for v0.8 of the [ ` uuid ` ] ( docs.rs/uuid/0.8 ) crate in the public API. | n/a | no |
51
51
52
52
## Overview of the BSON Format
53
53
@@ -208,14 +208,14 @@ that is also less error prone.
208
208
### Working with datetimes
209
209
210
210
The BSON format includes a datetime type, which is modeled in this crate by the
211
- [ ` bson::DateTime ` ] ( https://docs.rs/bson/2.0.0-beta.3 /bson/struct.DateTime.html ) struct, and the
211
+ [ ` bson::DateTime ` ] ( https://docs.rs/bson/latest /bson/struct.DateTime.html ) struct, and the
212
212
` Serialize ` and ` Deserialize ` implementations for this struct produce and parse BSON datetimes when
213
213
serializing to or deserializing from BSON. The popular crate [ ` chrono ` ] ( https://docs.rs/chrono ) also
214
214
provides a ` DateTime ` type, but its ` Serialize ` and ` Deserialize ` implementations operate on strings
215
215
instead, so when using it with BSON, the BSON datetime type is not used. To work around this, the
216
216
` chrono-0_4 ` feature flag can be enabled. This flag exposes a number of convenient conversions
217
217
between ` bson::DateTime ` and ` chrono::DateTime ` , including the
218
- [ ` chrono_datetime_as_bson_datetime ` ] ( https://docs.rs/bson/2.0.0-beta.3 /bson/serde_helpers/chrono_datetime_as_bson_datetime/index.html )
218
+ [ ` chrono_datetime_as_bson_datetime ` ] ( https://docs.rs/bson/latest /bson/serde_helpers/chrono_datetime_as_bson_datetime/index.html )
219
219
serde helper, which can be used to (de)serialize ` chrono::DateTime ` s to/from BSON datetimes, and the
220
220
` From<chrono::DateTime> ` implementation for ` Bson ` , which allows ` chrono::DateTime ` values to be
221
221
used in the ` doc! ` and ` bson! ` macros.
@@ -254,7 +254,7 @@ provide a UUID type (`Uuid`), though its `Serialize` and `Deserialize` implement
254
254
strings, so when using it with BSON, the BSON binary type will not be used. To facilitate the
255
255
conversion between ` Uuid ` values and BSON binary values, the ` uuid-0_8 ` feature flag can be
256
256
enabled. This flag exposes a number of convenient conversions from ` Uuid ` , including the
257
- [ ` uuid_as_binary ` ] ( https://docs.rs/bson/2.0.0-beta.3 /bson/serde_helpers/uuid_as_binary/index.html )
257
+ [ ` uuid_as_binary ` ] ( https://docs.rs/bson/latest /bson/serde_helpers/uuid_as_binary/index.html )
258
258
serde helper, which can be used to (de)serialize ` Uuid ` s to/from BSON binaries with the UUID
259
259
subtype, and the ` From<Uuid> ` implementation for ` Bson ` , which allows ` Uuid ` values to be used in
260
260
the ` doc! ` and ` bson! ` macros.
0 commit comments