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

Age	Commit message (Collapse)	Author	Lines
2014-03-15	log: Introduce liblog, the old std::logging	Alex Crichton	-9/+9
	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-11-26	librustc: Make `\|\|` lambdas not infer to `proc`s	Patrick Walton	-1/+1

2013-10-25	Remove ancient emacs mode lines from test cases	Brian Anderson	-1/+0
	These are relics that serve no purpose.
2013-10-22	Drop the '2' suffix from logging macros	Alex Crichton	-9/+9
	Who doesn't like a massive renaming?
2013-09-30	rpass: Remove usage of fmt!	Alex Crichton	-9/+9

2013-05-29	librustc: Stop reexporting the standard modules from prelude.	Patrick Walton	-0/+2

2013-05-19	Use assert_eq! rather than assert! where possible	Corey Richardson	-9/+9

2013-05-08	test: Fix tests.	Patrick Walton	-1/+1

2013-05-02	Remove 'Local Variable' comments	Brendan Zabarauskas	-8/+0

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

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

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

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

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

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

2012-09-11	Convert 'use' to 'extern mod'. Remove old 'use' syntax	Brian Anderson	-1/+1

2012-09-05	test: "import" -> "use"	Patrick Walton	-1/+1

2012-07-01	Convert to new closure syntax	Brian Anderson	-1/+1

2012-06-30	Eliminate usages of old sugared call syntax	Brian Anderson	-1/+1

2012-01-06	port over the tests to use the new API	Niko Matsakis	-1/+1

2011-12-22	Register new snapshots, purge log_err and log_full in favour of log(...).	Graydon Hoare	-9/+9

2011-12-22	Register snapshots and switch logging over to use of log_full or #error / ↵	Graydon Hoare	-9/+9
	#debug.
2011-12-13	Copy first batch of material from libstd to libcore.	Graydon Hoare	-1/+1

2011-11-17	remove compile-command from local variable blocks	Niko Matsakis	-1/+0

2011-10-20	Remove temporary fn# syntax	Brian Anderson	-1/+1

2011-10-20	Drop the 2 from the spawn*2 functions	Brian Anderson	-2/+2
	Issue #1022
2011-10-20	Convert tests to use bare-fn spawn	Brian Anderson	-4/+4
	Issue #1022
2011-08-25	Cleaning up task and comm exports, updating all the test cases.	Eric Holk	-2/+2

2011-08-15	Converted two more spawn tests.	Eric Holk	-1/+4

2011-08-03	Remove all xfail-stage0 directives	Brian Anderson	-1/+0
	While it is still technically possible to test stage 0, it is not part of any of the main testing rules and maintaining xfail-stage0 is a chore. Nobody should worry about how tests fare in stage0.
2011-07-27	Reformat for new syntax	Marijn Haverbeke	-31/+21

2011-07-13	Prohibit trailing whitespace under 'tidy' script. Clean up all caught cases.	Graydon Hoare	-1/+1

2011-06-15	Fixed a problem where spawn arguments were getting lost again. Also, fixed ↵	Eric Holk	-4/+10
	up stack alignment, which closes #496
2011-06-15	Fix a bunch of compile-command lines to use RBUILD	Graydon Hoare	-1/+1

2011-05-27	Re-XFAIL, not valgrind-clean.	Graydon Hoare	-0/+3

2011-05-27	Switching over to wrappers for spawning functions of multiple arguments. ↵	Eric Holk	-4/+29
	Doesn't quite work yet.
2011-05-27	Un-XFAILing spawn tests.	Eric Holk	-4/+0

2011-05-27	Working on 2 argument spawn. The arguments seem to be copied correctly once, ↵	Eric Holk	-0/+15
	but then they get lost.