Fixing a bunch of nightly fallouts

[farcaller]

This fixes lifetimes broken by lifetime elision.

Cleaning up lifetimes is tracked in #115.

Also fixed rlib dependency tracker, an issue with broken PT if compiled with -O2. Libcore version is now matched to rustc version to prevent any compilation failures.

[farcaller]

r?

[bgamari]

@farcaller am I mistaken in thinking that bors expects approvals to be of the form r+ on the last commit?

[farcaller]

bors allows that only from collaborators. Fixed that for you and @errordeveloper ;-)

[farcaller]

Another one thing that I cannot reproduce, and this code doesn't even touch PT!

/home/travis/build/hackndev/zinc/apps/app_empty.rs:1:1: 1:1 error: expected node path but found `=`
/home/travis/build/hackndev/zinc/apps/app_empty.rs:1 #![feature(phase, asm)]

[farcaller]

Ok, so this is nightly fallout in nightly fallout fix. Looking into it...

[farcaller]

Breakage investigation so far:

parser's let ttsvec = tts.iter().map(|x| (*x).clone()).collect(); is broken, it produces a Vec, that somehow starts with EQ token for no apparent reason. Also you can't print that vec, as rustc SIGSEGVs.

Replaced with let ttsvec = Vec::from_slice(tts);.

Now, quote_expr! in system_clock_pt's materialiser is broken as well (guess what, exactly the same error, "unexpected token: ="!).

I have absolutely no idea, what's happening in there, filed rust-lang/rust#15931

[farcaller]

Did a bisect and small investigation, rust-lang/rust#15972.

[farcaller]

Filed rust-lang/rust#15973.

[farcaller]

r? 😄

[errordeveloper]

👍