rust - https://github.com/rust-lang/rust

Age	Commit message (Collapse)	Author	Lines
2020-05-06	Move tests from `test/run-fail` to UI	Yuki Okushi	-24/+0

2018-12-25	Remove licenses	Mark Rousskov	-10/+0

2016-06-06	run rustfmt on test/run-fail folder	Srinivas Reddy Thatiparthy	-3/+9

2015-03-26	Mass rename uint/int to usize/isize	Alex Crichton	-3/+3
	Now that support has been removed, all lingering use cases are renamed.
2015-02-18	Fallout: tests. As tests frequently elide things, lots of changes	Niko Matsakis	-0/+4
	here. Some of this may have been poorly rebased, though I tried to be careful and preserve the spirit of the test.
2014-10-29	Rename fail! to panic!	Steve Klabnik	-2/+2
	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]
2013-10-22	Drop the '2' suffix from logging macros	Alex Crichton	-2/+2
	Who doesn't like a massive renaming?
2013-09-30	rfail: Remove usage of fmt!	Alex Crichton	-2/+2

2013-08-17	Fix warnings it tests	Erick Tryzelaar	-1/+1

2013-06-28	librustc: Change "Owned" to "Send" everywhere	Patrick Walton	-1/+1

2013-05-14	Use static string with fail!() and remove fail!(fmt!())	Björn Steinbrink	-1/+1
	fail!() used to require owned strings but can handle static strings now. Also, it can pass its arguments to fmt!() on its own, no need for the caller to call fmt!() itself.
2013-03-07	test: Fix tests.	Patrick Walton	-1/+4

2013-02-20	librustc: Separate most trait bounds with '+'. rs=plussing	Patrick Walton	-1/+1

2013-02-13	Remove die!, raplace invocations with fail! Issue #4524 pt 3	Nick Desaulniers	-2/+2

2013-01-31	Replace most invocations of fail keyword with die! macro	Nick Desaulniers	-2/+2

2013-01-29	librustc: Disallow trait bounds in types, enumerations, and structure ↵	Patrick Walton	-1/+1
	definitions. r=tjc
2012-12-13	Rename Send trait to Owned	Brian Anderson	-2/+2

2012-12-10	Reliciense makefiles and testsuite. Yup.	Graydon Hoare	-0/+10

2012-09-07	Convert all kind bounds to camel case. Remove send, owned keywords.	Brian Anderson	-2/+2

2012-08-13	De-mode-ify a few minor libcore modules.	Graydon Hoare	-2/+2

2012-07-14	Move the world over to using the new style string literals and types. Closes ↵	Michael Sullivan	-1/+1
	#2907.
2012-04-30	Stop inferring bot/static when types/regions are unconstrained.	Niko Matsakis	-1/+1
	Also, some other changes that came up along the way: - add a 'blk' region for the current block. - detect unused type/region variables.
2012-01-05	Switch to new param kind bound syntax	Marijn Haverbeke	-2/+2
	And remove support for the old syntax
2011-11-18	Update stdlib, compiler, and tests to new kind system	Marijn Haverbeke	-2/+2
	This involved adding 'copy' to more generics than I hoped, but an experiment with making it implicit showed that that way lies madness -- unless enforced, you will not remember to mark functions that don't copy as not requiring copyable kind. Issue #1177
2011-11-03	Update some more tests for 1a68a9882	Marijn Haverbeke	-1/+1

2011-10-28	Move to short kind kinds words in test suite	Marijn Haverbeke	-2/+2
	Issue #1076
2011-10-25	Update our code to new type parameter kind syntax	Marijn Haverbeke	-2/+2
	Closes #1067
2011-09-12	Pretty-print for new arg-mode syntax	Marijn Haverbeke	-1/+1

2011-08-20	Reformat	Brian Anderson	-8/+3
	This changes the indexing syntax from .() to [], the vector syntax from ~[] to [] and the extension syntax from #fmt() to #fmt[]
2011-08-16	Port the tests to the decl foo<T> syntax.	Erick Tryzelaar	-2/+2

2011-08-16	Port the tests to the typaram foo<T> syntax.	Erick Tryzelaar	-2/+2

2011-08-10	Use actual type, not declared type, when zeroing move arguments	Tim Chevalier	-0/+16
	trans was failing with a bounds check error because the caller was using the declared type (an out-of-scope ty param) and not the actual type in a list of argument types to zero. Closes #811