Rename task failure to task panic

[alexcrichton]

Tracking issue for rust-lang/rfcs#221

Nominating, as renaming the fail! macro to panic! is backwards incompatible. I believe updating all the documentation does not necessarily need to block 1.0.

[mdinger]

Can't you just do this to update everything immediately? I'm not sure why the documentation would lag since it would be updated as well...

$ cd rust-src/dir
$ grep -lZR 'fail!' . | xargs -0 -l sed -i -e 's/fail!/panic!/g'

[huonw]

@mdinger our documentation has things like "This fails if ...", and # Failure. (Most refer to fail!, but some refer to the general idea of "this operation may not succeed".)

[mdinger]

Ah, I see

[pnkfelix]

1.0, P-backcompat-libs.

[aturon]

@steveklabnik It would be good to coordinate the (easy) code change with the (harder) doc change. Do you have any thoughts here?

[steveklabnik]

Sure, want me to just do all of it? The code part should be pretty easy too.

[aturon]

@steveklabnik Sure, that'd be awesome!

One thing we should do as part of this is standardize the the markdown subsection for describing error outcomes. Let's talk about that on IRC when you get the chance.

[aturon]

@steveklabnik Just to be clear, the documentation change means not just the guide, but also all of the doc comments in libstd.

[steveklabnik]

Yup.