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

Age	Commit message (Collapse)	Author	Lines
2018-09-06	Migrated slew of run-pass tests to various subdirectories of `ui/run-pass/`.	Felix S. Klock II	-22/+0

2015-03-15	Strip all leading/trailing newlines	Tamir Duberstein	-1/+0

2014-04-14	Use new attribute syntax in python files in src/etc too (#13478)	Manish Goregaokar	-1/+1

2014-04-06	Remove check-fast. Closes #4193, #8844, #6330, #7416	Brian Anderson	-1/+0

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!"); }
2014-02-11	Change `xfail` directives in compiletests to `ignore`, closes #11363	Florian Hahn	-2/+2

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-08-17	Fix warnings it tests	Erick Tryzelaar	-0/+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-03-02	librustc: Forbid chained imports and fix the logic for one-level renaming ↵	Patrick Walton	-1/+1
	imports
2013-02-01	check-fast fallout from removing export, r=burningtree	Graydon Hoare	-1/+1

2013-01-30	test: Remove export from the tests, language, and libraries. rs=deexporting	Patrick Walton	-4/+2

2012-12-13	librustc: Make `use` statements crate-relative by default. r=brson	Patrick Walton	-0/+2

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

2012-09-21	Install new pub/priv/export rules as defaults, old rules accessible under ↵	Graydon Hoare	-0/+2
	#[legacy_exports];
2012-09-05	test: "import" -> "use"	Patrick Walton	-2/+2

2012-08-23	`m1!{...}` -> `m1!(...)`	Paul Stansifer	-1/+1

2012-07-30	Change syntax extension syntax: `#m[...]` -> `m!{...}`.	Paul Stansifer	-1/+1

2011-12-22	Register snapshots and switch logging over to use of log_full or #error / ↵	Graydon Hoare	-1/+1
	#debug.
2011-12-02	Make import ignore imports coming after them	Marijn Haverbeke	-1/+1
	This broke no code at all, so I guess people were already writing imports in this style. Issue #1228
2011-08-20	Reformat	Brian Anderson	-1/+1
	This changes the indexing syntax from .() to [], the vector syntax from ~[] to [] and the extension syntax from #fmt() to #fmt[]
2011-06-29	Make tests a little more friendly to combine.	Graydon Hoare	-1/+1

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

2011-05-12	Downcase std modules again, move to :: for module dereferencing	Marijn Haverbeke	-2/+2
	This should be a snapshot transition.
2011-01-07	Add sufficient import support to compile some simple single-crate programs.	Rafael Ávila de Espíndola	-0/+12
	This is likely not the final solution. It does repetitive work and doesn't produce errors for invalid but unused imports. In any case, I think it is a useful step.