- 28 5月, 2014 1 次提交
-
-
由 Alex Crichton 提交于
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]
-
- 22 5月, 2014 1 次提交
-
-
由 Alex Crichton 提交于
The new documentation site has shorter urls, gzip'd content, and index.html redirecting functionality.
-
- 13 5月, 2014 1 次提交
-
-
由 Brian Anderson 提交于
-
- 01 5月, 2014 1 次提交
-
-
由 Brendan Zabarauskas 提交于
This will allow us to provide type-safe APIs in libstd that are C-compatible.
-
- 30 4月, 2014 1 次提交
-
-
由 Brendan Zabarauskas 提交于
The `bitflags!` macro generates a `struct` that holds a set of C-style bitmask flags. It is useful for creating typesafe wrappers for C APIs. For example: ~~~rust #[feature(phase)]; #[phase(syntax)] extern crate collections; bitflags!(Flags: u32 { FlagA = 0x00000001, FlagB = 0x00000010, FlagC = 0x00000100, FlagABC = FlagA.bits | FlagB.bits | FlagC.bits }) fn main() { let e1 = FlagA | FlagC; let e2 = FlagB | FlagC; assert!((e1 | e2) == FlagABC); // union assert!((e1 & e2) == FlagC); // intersection assert!((e1 - e2) == FlagA); // set difference } ~~~
-
- 09 4月, 2014 1 次提交
-
-
由 Huon Wilson 提交于
-
- 05 4月, 2014 1 次提交
-
-
由 Alex Crichton 提交于
-
- 04 4月, 2014 1 次提交
-
-
由 Brian Anderson 提交于
This also changes some of the download links in the documentation to 'nightly'.
-
- 01 4月, 2014 2 次提交
-
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
- 29 3月, 2014 2 次提交
-
-
由 Brian Anderson 提交于
Closes #2569
-
由 Erick Tryzelaar 提交于
It was decided in a meeting that this module wasn't needed, and more thought should be put into a persistent collections library.
-
- 23 3月, 2014 1 次提交
-
-
由 Flavio Percoco 提交于
-
- 21 3月, 2014 2 次提交
-
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
It's now in the prelude.
-
- 16 3月, 2014 2 次提交
-
-
由 Alex Crichton 提交于
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!"); }
-
由 Steven Fackler 提交于
-
- 14 3月, 2014 1 次提交
-
-
由 Huon Wilson 提交于
This is useless at the moment (since pretty much every crate uses `~[]`), but should help avoid regressions once completely removed from a crate.
-
- 12 3月, 2014 1 次提交
-
-
由 Huon Wilson 提交于
-
- 28 2月, 2014 1 次提交
-
-
由 Erick Tryzelaar 提交于
-
- 25 2月, 2014 1 次提交
-
-
由 Alex Crichton 提交于
This also inverts the dependency between libserialize and libcollections. cc #8784
-
- 23 2月, 2014 1 次提交
-
-
由 Alex Crichton 提交于
These two containers are indeed collections, so their place is in libcollections, not in libstd. There will always be a hash map as part of the standard distribution of Rust, but by moving it out of the standard library it makes libstd that much more portable to more platforms and environments. This conveniently also removes the stuttering of 'std::hashmap::HashMap', although 'collections::HashMap' is only one character shorter.
-
- 20 2月, 2014 2 次提交
-
-
由 Liigo Zhuang 提交于
-
由 HeroesGrave 提交于
-
- 15 2月, 2014 1 次提交
-
-
由 Alex Crichton 提交于
This was previously implemented, and it just needed a snapshot to go through
-
- 07 2月, 2014 1 次提交
-
-
由 HeroesGrave 提交于
-