rust/src/test/compile-fail/coherence-blanket-conflicts-with-specific-multidispatch.rs, branch master https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=master 2018-08-14T08:38:00+00:00 Moved compile-fail tests to ui tests. 2018-08-14T08:38:00+00:00 David Wood david@davidtw.co 2018-08-08T12:28:26+00:00 urn:sha1:b16a30677f4e641329e768272cf9d3ecc2fa31c4 Adjust overlap-related tests to account for cosmetic changes to error reporting behavior 2016-03-14T22:04:37+00:00 Aaron Turon aturon@mozilla.com 2015-12-30T05:18:24+00:00 urn:sha1:d8160799b5c464ccdb99e4bab7196440106c1972 Kill fmt::Show and fmt::String with fire! 2015-02-21T14:27:55+00:00 Simonas Kazlauskas git@kazlauskas.me 2015-02-21T11:28:28+00:00 urn:sha1:e3104d8f0c3ceb3b268cd6ddc5e91f355e44a7c5 Toss the tomatoes! Update compile fail tests to use usize. 2015-01-08T16:02:24+00:00 Huon Wilson dbau.pp+github@gmail.com 2015-01-08T11:02:42+00:00 urn:sha1:85f961e2ccf056965fd7a95c44ce0922a865ae8d Use `derive` rather than `deriving` in tests 2015-01-02T10:05:22+00:00 Nick Cameron ncameron@mozilla.com 2014-12-31T04:32:49+00:00 urn:sha1:30e149231c627e61524d1b5bd6357886befae9e6 Rename fail! to panic! 2014-10-29T15:43:07+00:00 Steve Klabnik steve@steveklabnik.com 2014-10-09T19:17:22+00:00 urn:sha1:7828c3dd2858d8f3a0448484d8093e22719dbda0 https://github.com/rust-lang/rfcs/pull/221 The current terminology of "task failure" often causes problems when writing or speaking about code. You often want to talk about the possibility of an operation that returns a Result "failing", but cannot because of the ambiguity with task failure. Instead, you have to speak of "the failing case" or "when the operation does not succeed" or other circumlocutions. Likewise, we use a "Failure" header in rustdoc to describe when operations may fail the task, but it would often be helpful to separate out a section describing the "Err-producing" case. We have been steadily moving away from task failure and toward Result as an error-handling mechanism, so we should optimize our terminology accordingly: Result-producing functions should be easy to describe. To update your code, rename any call to `fail!` to `panic!` instead. Assuming you have not created your own macro named `panic!`, this will work on UNIX based systems: grep -lZR 'fail!' . | xargs -0 -l sed -i -e 's/fail!/panic!/g' You can of course also do this by hand. [breaking-change] Implement multidispatch and conditional dispatch. Because we do not 2014-10-09T21:19:50+00:00 Niko Matsakis niko@alum.mit.edu 2014-10-09T21:19:50+00:00 urn:sha1:389ef6601d18112a7a449eac2e190e4eb061bdf8 attempt to preserve crate concatenation, this is a backwards compatible change. Conflicts: src/librustc/middle/traits/select.rs