Utc::now() panicks when targetting WebAssembly

[jjpe]

I have a crate that uses chrono extensively, and I am trying to enable that crate to target WASM.

However, I've traced a panic! I'm getting to the UTC::now() constructor fn. Specifically:

#[cfg(feature="clock")]
impl Utc {
    // ...
    pub fn now() -> DateTime<Utc> {
        let spec = oldtime::get_time(); // <-- offending line
        let naive = NaiveDateTime::from_timestamp(spec.sec, spec.nsec as u32);
        DateTime::from_utc(naive, Utc)
    }
}

I'm hoping a fix for this can be as easy as an extra version of UTC::now() for WASM, but I'm unsure.

[jjpe]

I've added initial support for wasm32 @ PR #287.

[David-OConnor]

Note that this is still unmerged.

[jasonwilliams]

@quodlibetor @GuillaumeGomez are you able to help with this? Some projects targeting web assembly break because of this issue, looks like there's been a PR

[ctaggart]

I just ran into this. It looks like #331 has the minimal changes. Thank you @evq for picking this back up!

[pitdicker]

Fixed in #331.