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

Age	Commit message (Collapse)	Author	Lines
2014-10-02	tests: remove uses of Gc.	Eduard Burtescu	-23/+0

2014-07-26	Remove managed_box gate from tests	Brian Anderson	-1/+0
	No longer does anything.
2014-06-14	rustc: Obsolete the `@` syntax entirely	Alex Crichton	-2/+4
	This removes all remnants of `@` pointers from rustc. Additionally, this removes the `GC` structure from the prelude as it seems odd exporting an experimental type in the prelude by default. Closes #14193 [breaking-change]
2014-05-27	Move std::{reflect,repr,Poly} to a libdebug crate	Alex Crichton	-0/+2
	This commit moves reflection (as well as the {:?} format modifier) to a new libdebug crate, all of which is marked experimental. This is a breaking change because it now requires the debug crate to be explicitly linked if the :? format qualifier is used. This means that any code using this feature will have to add `extern crate debug;` to the top of the crate. Any code relying on reflection will also need to do this. Closes #12019 [breaking-change]
2014-04-14	Use new attribute syntax in python files in src/etc too (#13478)	Manish Goregaokar	-1/+1

2014-03-15	log: Introduce liblog, the old std::logging	Alex Crichton	-1/+1
	This commit moves all logging out of the standard library into an external crate. This crate is the new crate which is responsible for all logging macros and logging implementation. A few reasons for this change are: * The crate map has always been a bit of a code smell among rust programs. It has difficulty being loaded on almost all platforms, and it's used almost exclusively for logging and only logging. Removing the crate map is one of the end goals of this movement. * The compiler has a fair bit of special support for logging. It has the __log_level() expression as well as generating a global word per module specifying the log level. This is unfairly favoring the built-in logging system, and is much better done purely in libraries instead of the compiler itself. * Initialization of logging is much easier to do if there is no reliance on a magical crate map being available to set module log levels. * If the logging library can be written outside of the standard library, there's no reason that it shouldn't be. It's likely that we're not going to build the highest quality logging library of all time, so third-party libraries should be able to provide just as high-quality logging systems as the default one provided in the rust distribution. With a migration such as this, the change does not come for free. There are some subtle changes in the behavior of liblog vs the previous logging macros: * The core change of this migration is that there is no longer a physical log-level per module. This concept is still emulated (it is quite useful), but there is now only a global log level, not a local one. This global log level is a reflection of the maximum of all log levels specified. The previously generated logging code looked like: if specified_level <= __module_log_level() { println!(...) } The newly generated code looks like: if specified_level <= ::log::LOG_LEVEL { if ::log::module_enabled(module_path!()) { println!(...) } } Notably, the first layer of checking is still intended to be "super fast" in that it's just a load of a global word and a compare. The second layer of checking is executed to determine if the current module does indeed have logging turned on. This means that if any module has a debug log level turned on, all modules with debug log levels get a little bit slower (they all do more expensive dynamic checks to determine if they're turned on or not). Semantically, this migration brings no change in this respect, but runtime-wise, this will have a perf impact on some code. * A `RUST_LOG=::help` directive will no longer print out a list of all modules that can be logged. This is because the crate map will no longer specify the log levels of all modules, so the list of modules is not known. Additionally, warnings can no longer be provided if a malformed logging directive was supplied. The new "hello world" for logging looks like: #[phase(syntax, link)] extern crate log; fn main() { debug!("Hello, world!"); }
2013-10-23	register snapshots	Daniel Micay	-1/+1

2013-10-22	Drop the '2' suffix from logging macros	Alex Crichton	-1/+1
	Who doesn't like a massive renaming?
2013-09-30	rpass: Remove usage of fmt!	Alex Crichton	-1/+1

2013-07-17	librustc: Remove all uses of the `Copy` bound.	Patrick Walton	-1/+1

2013-07-17	Clean-up tests after debug!/std-macros change.	Huon Wilson	-1/+1
	The entire testsuite is converted to using info! rather than debug! because some depend on the code within the debug! being trans'd.
2013-05-19	Use assert_eq! rather than assert! where possible	Corey Richardson	-1/+1

2013-03-29	librustc: Remove `fail_unless!`	Patrick Walton	-1/+1

2013-03-11	Remove uses of log	Brian Anderson	-1/+1

2013-03-07	librustc: Convert all uses of `assert` over to `fail_unless!`	Patrick Walton	-1/+1

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

2013-02-01	check-fast fallout from removing export, r=burningtree	Graydon Hoare	-1/+1

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	-1/+1

2012-08-01	Convert ret to return	Brian Anderson	-1/+1

2012-01-05	Switch to new param kind bound syntax	Marijn Haverbeke	-1/+1
	And remove support for the old syntax
2011-12-22	Register new snapshots, purge log_err and log_full in favour of log(...).	Graydon Hoare	-1/+1

2011-12-22	Register snapshots and switch logging over to use of log_full or #error / ↵	Graydon Hoare	-1/+1
	#debug.
2011-11-18	Update stdlib, compiler, and tests to new kind system	Marijn Haverbeke	-1/+1
	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-10-25	Update our code to new type parameter kind syntax	Marijn Haverbeke	-1/+1
	Closes #1067
2011-09-12	Reformat for new mode syntax, step 1	Marijn Haverbeke	-1/+1
	Long lines were fixed in a very crude way, as I'll be following up with another reformat in a bit.
2011-08-23	Add kind-checking for assign-op, copy, ret, be, fail exprs. Fix caught ↵	Graydon Hoare	-1/+1
	kinding-violations in rustc and libstd.
2011-08-16	Port the tests to the expr foo::<T> syntax.	Erick Tryzelaar	-1/+1

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

2011-07-27	Reformat for new syntax	Marijn Haverbeke	-3/+3

2011-06-15	Reformat source tree (minus a couple tests that are still grumpy).	Graydon Hoare	-7/+6

2011-05-14	Remove xfail-boot lines from tests	Brian Anderson	-1/+0

2011-05-02	Un-revert "Use different syntax for checks that matter to typestate", fixing ↵	Patrick Walton	-1/+1
	the problem. This reverts commit d08b443fffb1181d8d45ae5d061412f202dd4118.
2011-05-02	Revert "Use different syntax for checks that matter to typestate"	Graydon Hoare	-1/+1
	This reverts commit aa25f22f197682de3b18fc4c8ba068d1feda220f. It broke stage2, not sure why yet.
2011-05-02	Use different syntax for checks that matter to typestate	Tim Chevalier	-1/+1
	This giant commit changes the syntax of Rust to use "assert" for "check" expressions that didn't mean anything to the typestate system, and continue using "check" for checks that are used as part of typestate checking. Most of the changes are just replacing "check" with "assert" in test cases and rustc.
2011-04-19	Un-XFAIL a few recently passing tests.	Graydon Hoare	-1/+0

2011-04-07	Add a test case for calling generic functions taking alias args with box types	Brian Anderson	-0/+13