xeos
/
chrono
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

0.1.17: language changes. 

- Many unstable stdlib parts require `#[feature]` flags as per
  Rust RFC #507.
This commit is contained in:
Kang Seonghoon 2015-01-30 00:02:48 +09:00
parent 7087cd156a
commit 36181b65ca
3 changed files with 5 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Cargo.toml
View File

@ -1,6 +1,6 @@
[package] [package]
name = "chrono" name = "chrono"
version = "0.1.16" version = "0.1.17"
authors = ["Kang Seonghoon <public+rust@mearie.org>"] authors = ["Kang Seonghoon <public+rust@mearie.org>"]
description = "Date and time library for Rust" description = "Date and time library for Rust"

2
README.md
View File

@ -1,4 +1,4 @@
[Chrono][doc] 0.1.16 [Chrono][doc] 0.1.17
==================== ====================
[![Chrono on Travis CI][travis-image]][travis] [![Chrono on Travis CI][travis-image]][travis]

8
src/lib.rs
View File

@ -4,7 +4,7 @@
/*! /*!
# Chrono 0.1.16 # Chrono 0.1.17
Date and time handling for Rust. (also known as `rust-chrono`) Date and time handling for Rust. (also known as `rust-chrono`)
It aims to be a feature-complete superset of the [time](https://github.com/rust-lang/time) library. It aims to be a feature-complete superset of the [time](https://github.com/rust-lang/time) library.
@ -78,7 +78,6 @@ Addition and subtraction is also supported.
The following illustrates most supported operations to the date and time: The following illustrates most supported operations to the date and time:
~~~~ {.rust} ~~~~ {.rust}
# #![allow(unstable)]
# /* we intentionally fake the datetime... # /* we intentionally fake the datetime...
use chrono::{UTC, Local, Datelike, Timelike, Weekday, Duration}; use chrono::{UTC, Local, Datelike, Timelike, Weekday, Duration};
@ -120,7 +119,6 @@ which format is equivalent to the familiar `strftime` format.
The default `to_string` method and `{:?}` specifier also give a reasonable representation. The default `to_string` method and `{:?}` specifier also give a reasonable representation.
~~~~ {.rust} ~~~~ {.rust}
# #![allow(unstable)]
use chrono::{UTC, Offset}; use chrono::{UTC, Offset};
let dt = UTC.ymd(2014, 11, 28).and_hms(12, 0, 9); let dt = UTC.ymd(2014, 11, 28).and_hms(12, 0, 9);
@ -140,7 +138,6 @@ Most operations available to `DateTime` are also available to `Date` and `Time`
whenever appropriate. whenever appropriate.
~~~~ {.rust} ~~~~ {.rust}
# #![allow(unstable)]
use chrono::{UTC, Local, Offset, LocalResult, Datelike, Weekday}; use chrono::{UTC, Local, Offset, LocalResult, Datelike, Weekday};
# // these *may* fail, but only very rarely. just rerun the test if you were that unfortunate ;) # // these *may* fail, but only very rarely. just rerun the test if you were that unfortunate ;)
@ -188,7 +185,8 @@ Advanced offset handling and date/time parsing is not yet supported (but is plan
#![doc(html_root_url = "https://lifthrasiir.github.io/rust-chrono/")] #![doc(html_root_url = "https://lifthrasiir.github.io/rust-chrono/")]
#![allow(unstable)] #![feature(core, collections, hash, std_misc)] // lib stability features as per RFC #507
#![cfg_attr(test, feature(test))] // ditto
#![deny(missing_docs)] #![deny(missing_docs)]
extern crate "time" as stdtime; extern crate "time" as stdtime;