Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upCookbook ideas for chrono #324
Comments
budziq
added this to the impl period milestone
Oct 9, 2017
budziq
added
the
tracking issue
label
Oct 9, 2017
This comment has been minimized.
This comment has been minimized.
|
Initial ideas by @j-haj
Once we get some attention here, I'll stsrt adding final example ideas to the tracking list. Thanks a lot @j-haj ! |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
@hegza Sounds great - can't wait to see the examples! One thing I noticed the other day is that chrono seems to state that it is not really best used for tracking elapsed time to execute a segment of code:
I'm wondering if maybe the first item in our list should be removed. @budziq what are your thoughts? |
This comment has been minimized.
This comment has been minimized.
|
Seems so. I would agree with just skipping that first one, since it would be hardly idiomatic to do something that the crate is not supposed to do. Another question I had in mind was that if the chrono examples should be assigned under some one of the current top-level topics, or if it should be a new topic. It seems that the topics are not trying to be library-by-library, but rather something more abstract. Formatting date-time could certainly be situated in more than just one of the current topics. |
This comment has been minimized.
This comment has been minimized.
Excellent question. Probably something for @budziq to chime in on but my intuition is that it makes the most sense to add this to basics section. It may not be super important as it sounds like we may reorganize things in the future. |
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Oct 23, 2017
This comment has been minimized.
This comment has been minimized.
Yep this item is a viable example idea but would be
Aaron is working on an editorial pass over the cookbook examples including section reorganization. For now lets add it to basics as @j-haj suggests. |
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Oct 25, 2017
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Oct 25, 2017
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Oct 25, 2017
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Oct 26, 2017
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Oct 26, 2017
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Oct 26, 2017
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Oct 29, 2017
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Oct 31, 2017
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Oct 31, 2017
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Oct 31, 2017
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Oct 31, 2017
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Oct 31, 2017
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Oct 31, 2017
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Oct 31, 2017
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Nov 2, 2017
budziq
added a commit
that referenced
this issue
Nov 3, 2017
This comment has been minimized.
This comment has been minimized.
|
For now such example would require a nondefault crate feature (explicitly enabling "serde" in cargo toml). As we have no clear story yet on howto support cargo features (how do we test these, how do we present cargo.toml and how to handle desynchronization with https://play.rust-lang.org/ which does not support crate features) Lets put it on back-burner for now |
This was referenced Nov 3, 2017
This comment has been minimized.
This comment has been minimized.
|
Two additional examples:
Do you think these could be interesting recipes? If you are happy with it, I can open dedicated issues for them. |
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Nov 4, 2017
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Nov 4, 2017
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Nov 4, 2017
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Nov 4, 2017
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Nov 4, 2017
This comment has been minimized.
This comment has been minimized.
Very cool ideas! Lets go for it |
hegza
pushed a commit
to hegza/rust-cookbook
that referenced
this issue
Nov 4, 2017
This was referenced Nov 5, 2017
This comment has been minimized.
This comment has been minimized.
|
As all the proposed ideas are implemented, I'm going to close the tracking issue. If you have additional ideas for Chrono, please feel free to open a new issue. The one outstanding issue mentioned is reorganization. That is definitely in the works. |
j-haj commentedOct 9, 2017
•
edited by budziq
Let's add some recipes for the
chronocrate. Feel free to contribute additional examples/ideas or PRs!DateTimestruct from input using RFC 2822, RFC 3339, and custom formatsDatelikeandTimeliketraits such as month, weekday, hour, minute, etc.