- 27 6月, 2013 9 次提交
-
-
由 Philipp Brüschweiler 提交于
-
由 Philipp Brüschweiler 提交于
-
由 Alex Crichton 提交于
-
由 Brian Anderson 提交于
-
由 Kevin Ballard 提交于
Move all the colors into a nested mod named color instead of prefixing with "color_". Define a new type color::Color, and make this a u16 instead of a u8 (to allow for easy comparisons against num_colors, which is a u16). Remove color_supported and replace it with num_colors. Teach fg() and bg() to "dim" bright colors down to the normal intensity if num_colors isn't high enough. Remove unnecessary copies, and fix a bug where a terminfo parse failure would try to use the wrong error and end up failing.
-
由 Ben Blum 提交于
-
由 Ramkumar Ramachandra 提交于
So --remote can work. Signed-off-by: NRamkumar Ramachandra <artagnon@gmail.com>
-
由 bors 提交于
r?
-
由 bors 提交于
flat_map_ produces an iterator that maps each element to an iterator, and yields the elements of the produced iterators. This is the monadic bind :: M a -> (a -> M b) -> M b for iterators. Named just like the vec method, but with a trailing underline until the method resolution bug is resolved. We discussed the name chain_map, but I decided to go with flat_map_ for consistency with vec. Since it.map(f).flatten() would be the same as it.flat_map(f), we could choose to just implement a flatten method instead. Either way the possibilities are the same but flat_map is more convenient.
-
- 26 6月, 2013 23 次提交
-
-
由 bors 提交于
This allows macros to both be conditionally defined, and expand to items with #[cfg]'s. This seems to have a performance improvement, e.g. for `std`: ``` # Before time: 1.660 s expansion time: 0.125 s configuration # After time: 0.080 s configuration 1 time: 1.127 s expansion time: 0.132 s configuration 2 ``` And for `extra`: ``` # Before time: 0.593 s expansion time: 0.062 s configuration # After time: 0.047 s configuration 1 time: 0.147 s expansion time: 0.058 s configuration 2 ``` (This seems a little peculiar, but it is possibly because the expansion AST traversal is very slow, so removing as much as possible as early as possible has big benefits.)
-
由 Huon Wilson 提交于
This allows macros to both be conditionally defined, and expand to items with #[cfg]'s.
-
由 bors 提交于
This PR contains no real code changes. Just some documentation additions in the form of comments and some internal reordering of functions within debuginfo.rs.
-
由 bors 提交于
-
由 bors 提交于
Reopening of #7031, Closes #6963 I imagine though that this will bounce in bors once or twice... Because attributes can't be cfg(stage0)'d off, there's temporarily a lot of new stage0/stage1+ code.
-
由 bors 提交于
Closes #7071
-
由 bors 提交于
Finally rename finalize to drop. Closes #4332.
-
由 Luqman Aden 提交于
-
由 bors 提交于
Sets the stage for further cleanup (especially mass-slaughter of `@`)
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 Corey Richardson 提交于
-
由 bors 提交于
-
由 Daniel Micay 提交于
-
由 Daniel Micay 提交于
-
由 Daniel Micay 提交于
the maps are being migrated to external iterators
-
由 Daniel Micay 提交于
-
由 Corey Richardson 提交于
-
由 bors 提交于
Fix #7322. I started out with a band-aid approach to special-case the duplicate module error using `is_duplicate_module`, but thought this would be better in the long term.
-
由 Ramkumar Ramachandra 提交于
The "first definition of ..." error string reported by add_child() looks different from similar messages reported by other functions. Fix this. Signed-off-by: NRamkumar Ramachandra <artagnon@gmail.com>
-
由 Ramkumar Ramachandra 提交于
add_child() is responsible for reporting errors about type, value, and module duplicate definitions. Although it checks for all three, it uses namespace_to_str() to convert a Namespace value into a string before printing an error like: error: duplicate definition of type `foo` ^^^^ note: first definition of type foo here: ^^^^ Unfortunately, this string can only be one of "type" or "value" (corresponding to TypeNS and ValueNS respectively), and it reports duplicate modules as duplicate types. To alleviate the problem, define a special NamespaceError enum to define more specialized errors, and use it instead of attempting to reuse the Namespace enum. Reported-by: NCorey Richardson <corey@octayn.net> Signed-off-by: NRamkumar Ramachandra <artagnon@gmail.com>
-
由 Michael Sullivan 提交于
-
由 bors 提交于
This is an attempt at a smaller request than #7113, it's just the first two commits
-
- 25 6月, 2013 8 次提交
-
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
-
由 bors 提交于
This adds a `#[no_drop_flag]` attribute. This attribute tells the compiler to omit the drop flag from the struct, if it has a destructor. When the destructor is run, instead of setting the drop flag, it instead zeroes-out the struct. This means the destructor can run multiple times and therefore it is up to the developer to use it safely. The primary usage case for this is smart-pointer types like `Rc<T>` as the extra flag caused the struct to be 1 word larger because of alignment. This closes #7271 and #7138
-
由 bors 提交于
This sets the `get_tydesc()` return type correctly and removes the intrinsic module. See #3730, #3475. Update: this now also removes the unused shape fields in tydescs.
-
由 bors 提交于
This adds both `static mut` items and `static mut` foreign items. This involved changing far less code than I thought it was going to, but the tests seem to pass and the variables seem functional. I'm more than willing to write more tests, so suggestions are welcome! Closes #553
-
由 bors 提交于
I also cleaned up the warnings.
-
由 James Miller 提交于
-
由 James Miller 提交于
-