7b612e9ae0
Merge pull request #261 from storyfeet/format-pointer
...
Tried to make it easier to find specifiers
2018-07-18 21:54:53 -04:00
611abbd7ae
trivially copy pass by ref
2018-07-18 21:38:37 -04:00
b9b09b8e11
Tried to make it easier to find specifiers
2018-07-18 21:38:37 -04:00
a88ee8f719
Fix doc
2018-07-18 04:45:11 -05:00
4a66b17bd0
Add docs/tests and fix math
2018-07-04 14:12:36 -05:00
5df91c3985
Add WIP millisecond serde implementation
2018-07-04 10:38:39 -05:00
e165a93a6c
Merge pull request #254 from LuoZijun/patch-1
...
Add Hash trait on FixedOffset
2018-06-24 13:29:53 -04:00
a99dee655e
Update fixed.rs
2018-06-24 05:45:24 +08:00
237042365e
Update for 0.4.4
2018-06-23 17:32:44 -04:00
7baafafc0c
Merge pull request #251 from emschwartz/master
...
Add nanoseconds without dots
2018-06-17 12:30:37 -04:00
df4912a33f
Test formatting with more precise nanoseconds
...
There is some specific behavior around writing out truncated nanos that we want
to be sure to preserve.
2018-06-13 23:00:31 -04:00
11cfb3696e
Move NanosecondXNoDot to internal enum
...
To avoid adding new variants to the public enum (see https://github.com/chronotope/chrono/pull/251#issuecomment-396692148 )
2018-06-12 14:53:49 -04:00
937189ee52
Take exactly num digits specified for nanosecond fixed
...
Error if it's too long or short, and don't take any more digits
2018-06-12 10:51:38 -04:00
8a2b09962a
Only parse up to max number of digits for nanoseconds w/o dots
2018-06-12 10:51:38 -04:00
074e92fc63
Document millisecond format without the dot
2018-06-12 10:51:36 -04:00
f9d3094d4e
Test nanosecond parsing without the dot
2018-06-12 10:51:07 -04:00
1de3658433
Add nanoseconds without dots
2018-06-12 10:51:07 -04:00
0ef8c5cc83
Bump Chrono Version to 0.4.3
2018-06-10 21:36:36 -04:00
f1852a6d21
Update changelog with TZ Offset Permissive
2018-06-10 21:35:41 -04:00
3c6e807672
Merge pull request #242 from quodlibetor/add-permissive-tz-parsing
...
Add %#z as "Permissive" timezone parsing
2018-06-10 20:38:09 -04:00
c3207a5811
Use the `InternalFixed` struct for TimezoneOffsetPermissive
...
It is the backcompat scheme that we have. In the 5.x timeline we will add the
more-standard and significantly-more-pleasant-to-expand `#[doc(hidden)]
__DoNotMatchAgainstMe` trick.
2018-06-07 21:46:57 -04:00
9991c2b0ed
Rust 1.13 does not support elided lifetimes in const.
2018-06-07 21:46:57 -04:00
95f6a2be1c
Add %#z as "Permissive" timezone parsing
...
This allows you to parse a timezone that:
* Is either `Z` or an actual offset
* Contains no minutes, just the hour
Fixes #219
2018-06-07 21:46:57 -04:00
9276929c58
Merge pull request #247 from HarkonenBade/nanosecond-ts
...
Nanosecond Timestamps
2018-05-24 13:19:39 -04:00
5d86c53679
Updated Changelog
2018-05-24 13:49:23 +01:00
90c75885d0
Rename ts_nano_seconds to ts_nanoseconds
2018-05-24 13:44:12 +01:00
cdb6170f02
Add serde functions for nanosecond timestamps
2018-05-18 11:05:03 +01:00
cc613976a4
Add functions to present DateTime in nanoseconds since epoch
2018-05-18 11:04:39 +01:00
92e1e7d7aa
Merge pull request #241 from gitter-badger/gitter-badge-1
...
Add a Gitter chat badge to README.md
2018-04-30 14:33:39 -04:00
66005be6a2
Fix position of gitter badge.
2018-04-19 23:28:09 -04:00
c2753f1158
Add Gitter badge
2018-04-20 03:23:21 +00:00
97dbfd02ab
Bump version for 0.4.2 release
2018-04-07 17:51:56 -04:00
1c4fc66323
Update changelog
2018-04-03 22:36:08 -04:00
ebd16f49d2
Merge pull request #237 from tobz1000/datetime-diff-sub
...
impl Sub<T> for T for Date/Time types
2018-04-03 19:30:15 -07:00
73ba5d7985
Merge pull request #236 from jethrogb/feature_clock
...
Optionally remove time crate dependency
2018-04-03 09:27:56 -07:00
19466e6ff4
Move `SubAssign<OldDuration> next to `Sub<OldDuration`
2018-04-03 14:16:37 +01:00
d9a50cb767
Documentation
2018-04-03 14:14:52 +01:00
a9618c8e9d
Merge branch 'master' into feature_clock
2018-04-03 05:54:17 -07:00
a060684abe
Merge pull request #174 from quodlibetor/deprecated-warnings-for-rustc_serialize
...
Deprecated warnings in cargo output for rustc-serialize feature
2018-04-03 05:52:58 -07:00
964d0a2070
Merge pull request #234 from skierpage/patch-1
...
Update version number to 0.4.1
2018-04-03 05:52:30 -07:00
d5d5fd92b7
impl Sub<T> for <T> for Date/Time types
2018-04-03 13:42:03 +01:00
5e68c60bb2
Add clock feature
2018-04-02 08:35:27 -07:00
ba1b88ecbc
Remove version number from README
2018-04-01 20:08:47 -04:00
21d302f0d2
Update version number to 0.4.1
...
cargo.toml and crates.io are at 0.4.1. I don't know if you want to update the docs link and sample `Cargo.toml` lines.
2018-04-01 17:02:32 -07:00
5aabc29a1f
Merge pull request #232 from phansch/master
...
Revert "Allow a false-positive clippy lint" as it has been fixed in clippy
2018-04-01 19:00:21 -04:00
3fb0b614e8
Revert "Allow a false-positive clippy lint"
...
The issue has been fixed with the latest clippy release and we don't
have to `allow` anymore.
This reverts commit 7f990144cc
2018-04-01 12:40:14 +02:00
6c398ae6f4
Remove dependencies from oldtime::Duration on rest of time crate
2018-03-30 16:08:45 -07:00
5e730ebe4d
Vendor oldtime::duration module from time crate
...
https://github.com/rust-lang-deprecated/time/blob/master/src/duration.rs
2018-03-30 16:08:45 -07:00
c368bf16d0
Adjust features selection in CI
2018-03-30 16:08:45 -07:00
39ca2e622c
Deprecated warnings in cargo output for rustc-serialize feature
...
Unfortunately due to rust-lang/rust#39935 placing the annotation on the `impl`s
of `Encodable`/`Decodable` for the various items have no effect whatsoever, so
we need to place it on some type that chrono actually uses internally. The only
*type* that I can find that only exists for rustc-serialize only is the
`TsSeconds` struct.
So, marking TsSeconds deprecated causes Chrono's internal uses of `TsSeconds`
to emit deprecation warnings, both in our builds and for packages that specify
Chrono as a dependency with the `rustc-serialize` feature active. This means
that the current commit will cause a `warning: use of deprecated item:
RustcSerialize will be removed before chrono 1.0, use Serde instead` to appear
in `cargo build` output.
Unfortunately I don't think that it's possible for downstream crates to disable
the warning the warning in any way other than actually switching to Serde or
using an older chrono. That's the reason for all the `#[allow(deprecated)]`
through the code, it means that the warning appears almost exactly once,
instead of dozens of times.
2018-03-29 14:32:39 -04:00
Brandon W Maister
storyfeet
novacrazy
寧靜
Evan Schwartz
Thomas Bytheway
The Gitter Badger
Toby Dimmick
Jethro Beekman
skierpage
Philipp Hansch