From 126943083ea96848acf4f03d11207c70d151dc53 Mon Sep 17 00:00:00 2001 From: quellen-sol Date: Tue, 7 Jan 2025 16:10:19 -0700 Subject: [PATCH] docs: fix typo in DateTime64 description --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d6f58e3..157a47a 100644 --- a/README.md +++ b/README.md @@ -367,7 +367,7 @@ How to choose between all these features? Here are some considerations: } ``` -* `DateTime64(_)` maps to/from `i32` or a newtype around it and represents a time elapsed since UNIX epoch. Also, [`time::OffsetDateTime`](https://docs.rs/time/latest/time/struct.OffsetDateTime.html) is supported by using `serde::time::datetime64::*`, that requires the `time` feature. +* `DateTime64(_)` maps to/from `i64` or a newtype around it and represents a time elapsed since UNIX epoch. Also, [`time::OffsetDateTime`](https://docs.rs/time/latest/time/struct.OffsetDateTime.html) is supported by using `serde::time::datetime64::*`, that requires the `time` feature.
Example