Giters
chronotope
/
chrono
Date and time library for Rust
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
3174
Watchers:
27
Issues:
630
Forks:
508
chronotope/chrono Issues
Ergonomic replacements for panicking APIs.
Updated
15 days ago
Comments count
14
Saturating operations
Updated
15 days ago
Comments count
3
Datetime Parse Error when converting rfc2822 date to chrono Datetime
Closed
23 days ago
Comments count
2
NaiveDate::years_since wrong documentation
Closed
a month ago
Parsing from string to DateTime - input is not enough for unique date and time
Updated
a month ago
Comments count
3
TimeDelta always returning a PT in seconds
Closed
a month ago
Comments count
2
How do I get the raw underlying bytes of a `NaiveDate`
Closed
a month ago
Comments count
4
Parsing numeric literals can cause TooShort/Invalid
Updated
2 months ago
Comments count
8
0.4.37 semver-incompatibly removes trait bounds on `DateTime`
Closed
2 months ago
Comments count
10
Releases has problematic naming of 0.4.8 release which puts it at the top
Closed
2 months ago
Comments count
3
Add a method to the `Offset` trait to return DST info
Updated
2 months ago
Comments count
5
0.5: Add a `LocalOffset` type
Updated
2 months ago
Comments count
4
`gh-pages` branch
Closed
2 months ago
Comments count
3
Verification of published packages
Closed
2 months ago
Comments count
2
Make Weekday::num_days_from public
Closed
2 months ago
Comments count
2
Tracking issue: Converting the API to return `Result`s
Updated
2 months ago
Comments count
19
0.5: Consider using smaller types for arguments
Updated
2 months ago
the trait bound `DateTime<Utc>: OptionFrom/ToWasmAbi` is not satisfied when targeting wasm32
Closed
2 months ago
Comments count
3
"input is not enough" for DateTime::parse_from_str but works for Utc.datetime_from_str
Closed
2 months ago
Comments count
2
Version 0.4.36 has breaking changes with 0.4.35
Closed
2 months ago
Comments count
2
Deprecations causing large amount of churn, and result in less elegant code
Closed
2 months ago
Comments count
3
Compile error using most recent version of chrono 0.4.36
Closed
2 months ago
Comments count
2
Is there a way to instantiate DateTimes over a generic TimeZone type?
Closed
2 months ago
Comments count
3
Use `localtime_rz` on Android if available
Updated
3 months ago
Consistently name methods that turn into another more complete type
Updated
3 months ago
Comments count
8
Deserializing DateTime from unix timestamp is not implemented, despite description
Closed
3 months ago
Comments count
1
Index out of bounds: the len is 733 but the index is 798
Closed
3 months ago
Comments count
11
Proper way to build a DateTime from another DateTime's Date
Closed
3 months ago
Comments count
3
0.5.x: Timezone conversion result (`LocalResult`)
Updated
3 months ago
Comments count
39
function Utc::now().checked_add_signed raised wrong error
Closed
3 months ago
Comments count
7
RFC: Bring some of the Rubedo extensions for Chrono into Chrono
Updated
3 months ago
Comments count
24
Breaking change in chrono 0.4.32 (Accepted MAX date changed)
Closed
3 months ago
Comments count
4
Deprecate panicking `TimeDelta` initializers
Closed
3 months ago
Comments count
2
Panic with TZ="pBB24"
Updated
3 months ago
Comments count
1
`TimeDelta::num_microseconds` (?)
Closed
3 months ago
Deprecate all timestamp-related methods on `NaiveDateTime`
Closed
3 months ago
Comments count
1
Properly support padding in parsers
Updated
3 months ago
Comments count
2
Inconsistent crate features documentation
Closed
3 months ago
Comments count
2
`DateTime` equality with different `Offset`s
Closed
3 months ago
Comments count
6
RFC: add feature "abi_stable" and make types abi stable
Closed
3 months ago
Comments count
7
Is there a simpler way to get the current date at a specific time?
Updated
4 months ago
Comments count
3
`Utc::now` can fail with dates that are very far into the past/future
Closed
4 months ago
Comments count
1
Differences between this crate and `time`
Updated
4 months ago
Comments count
12
Mark `format::Numeric` and `format::Fixed` as `non_exhaustive`
Closed
4 months ago
Comments count
5
Consider reverting #807 on the 0.5 branch
Updated
4 months ago
Comments count
1
Help understanding Parsing error: NotEnough while using parse_from_str
Closed
4 months ago
Comments count
3
Supporting normalising dates/times
Updated
4 months ago
Comments count
4
Recognize our review capacity is limited for non-trivial work
Updated
4 months ago
Comments count
7
`DateTime::years_since` is tricky during ambiguous local time
Updated
4 months ago
Comments count
5
string parse with user specified format.
Closed
4 months ago
Comments count
2
Previous
Next