Upgrade to rustc 1.0.0-nightly (6790b0e51 2015-04-11) (built 2015-04-12)

[SimonSapin]

Also disable doctests because of rust-lang/cargo#1512

Note that there weren’t any doctest to run anyway.

r? @kmcallister

[kmcallister]

These should go back to = "0" unless there's a reason to keep them pinned.

[SimonSapin]

Semver says anything goes before 1.0, but Cargo’s extrapolation of it is that any 0.7.x should be compatible with 0.7.y with y <= x, while 0.8 is not. So if phf follows that convention, 0.8 will probably break html5ever while (in a post-Rust-1.0 world) 0.7 will still be available and compatible.

That said, I’ll make them = "0" if you still feel it’s the right thing to do.

[kmcallister]

Okay, = "0.7" works for me.

[kmcallister]

Why do we need this instead of Result::unwrap()?

[SimonSapin]

This is what libsyntax does:

https://github.com/rust-lang/rust/blob/b9ed9e2a326cafa6f2445aec7221dc419089cf5f/src/libsyntax/lib.rs#L53-L56

A variant of 'try!' that panics on Err(FatalError). This is used as a crutch on the way towards a non-panic!-prone parser. It should be used for fatal parsing errors; eventually we plan to convert all code using panictry to just use normal try

Right now it’s the same as .unwrap, but the plan is apparently that it should be try! eventually.

[kmcallister]

Ah, can you add a link or reference to that libsyntax code in a comment here? And, is there an associated Rust issue number?

[kmcallister]

Thanks! r=me with the link or reference to libsyntax as mentioned above.