Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't require time crate for clock feature #478

Merged
merged 1 commit into from
Sep 25, 2020

Commits on Sep 23, 2020

  1. Don't require time crate for clock feature

    Absorb just enough of the time crate that it is no longer required for
    the clock feature. v0.1 of the time crate is long deprecated, and v0.2 of
    the crate is a complete rewrite.
    
    Vendoring v0.1 allows chrono to control its own destiny. It also means
    that downstream users that have upgraded to the time v0.2 ecosystem do
    not wind up with both time v0.1 and v0.2 in the dependency tree.
    
    Even with this patch, the dependency on the old time crate remains by
    default for backwards compatibility. Specifically, the
    `chrono::Duration` type is a re-export of the `time::Duration` type when
    the `oldtime` feature is enabled, as it is by default. The intent is
    that the `oldtime` feature will be removed when chrono v0.5 is released.
    
    Supersedes chronotope#286.
    Fixes chronotope#400.
    benesch committed Sep 23, 2020
    Configuration menu
    Copy the full SHA
    c8cf743 View commit details
    Browse the repository at this point in the history