- 15 9月, 2013 30 次提交
-
-
由 blake2-ppc 提交于
Remove these in favor of the two traits themselves and the wrapper function std::from_str::from_str. Add the function std::num::from_str_radix in the corresponding role for the FromStrRadix trait.
-
由 bors 提交于
This follows from the discussion in #9012. * All macros are now defined in terms of `format_args!` allowing for removal of a good bit of code in the syntax extension * The syntax extension is now in a more aptly-named file, `format.rs` * Documentation was added for the `format!`-related macros.
-
由 Alex Crichton 提交于
The same fix as before is still relevant, I just forgot to update the expand_stmt macro expansion site. The tests for format!() suffice as tests for this change.
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
This renames the syntax-extension file to format from ifmt, and it also reduces the amount of complexity inside by defining all other macros in terms of format_args!
-
由 bors 提交于
-
由 Daniel Micay 提交于
-
由 bors 提交于
r? @metajack - This solves the problem you were having earlier with things like ```extern mod geom = "rust-geom";``` (or something like that).
-
由 Daniel Micay 提交于
-
由 Daniel Micay 提交于
The cases they test are well covered in the `std::iter` tests.
-
由 Tim Chevalier 提交于
For some reason, I thought it wasn't necessary to write the package_id attribute (which rustc's filesearch checks when searching for a package) if the package ID had a single component (like "foo") as opposed to multiple components (like "foo/bar/quux"). This meant that `extern mod quux = "an-awesome-library";` didn't work, even if an-awesome-library existed in the RUST_PATH. Fixed it.
-
由 blake2-ppc 提交于
Replaced by `std::iter::range_step`
-
由 blake2-ppc 提交于
Use the iterator version instead of the old uint::/int::range_step functions.
-
由 Daniel Micay 提交于
-
由 Daniel Micay 提交于
-
由 Daniel Micay 提交于
-
由 bors 提交于
-
由 bors 提交于
My focus was on getting these to be correct in all cases by handling overflow properly. I'll clean them up and work on the performance later.
-
由 Lindsey Kuper 提交于
-
由 Lindsey Kuper 提交于
-
由 Daniel Micay 提交于
-
由 bors 提交于
SharedPort implementation was missing in std::comm. Since this module also wraps SharedChan, it makes sense to have SharedPort defined there as well.
-
由 bors 提交于
Allows `std::rt::io::timer::sleep(1000)` rather than `std::rt::io::timer::Timer::new().unwrap().sleep(1000)`.
-
由 Daniel Micay 提交于
-
由 Daniel Micay 提交于
-
由 Flavio Percoco 提交于
SharedPort implementation was missing in std::comm. Since this module also wraps SharedChan, it makes sense to have SharedPort defined there as well.
-
由 Daniel Micay 提交于
-
由 bors 提交于
Closes #5794
-
由 bors 提交于
Somehow this was missed! cc #4819
-
由 bors 提交于
I'm getting the three `make check` failures mentioned in issue #9127, which I also get building master.
-
- 14 9月, 2013 10 次提交
-
-
由 bors 提交于
Work a bit towards #9157 "Remove Either". These instances don't need to use Either and are better expressed in other ways (removing allocations and simplifying types).
-
由 bors 提交于
-
由 Huon Wilson 提交于
-
由 bors 提交于
An expression such as `bottom == not_bottom` or `not_bottom == bottom` already compiled, but this fixes the case where both sides are `bottom`.
-
由 bors 提交于
It was broken on win32 because of header inconsistency.
-
由 bors 提交于
Closes #9123
-
由 bors 提交于
Remove references to local_data::Key and only mention the macro for how to construct new keys into local data.
-
由 bors 提交于
This is a workaround for #9155. Currently, any uses of BufferedStream outside of libstd ICE.
-
由 bors 提交于
This is a series of patches to modernize option and result. The highlights are: * rename `.unwrap_or_default(value)` and etc to `.unwrap_or(value)` * add `.unwrap_or_default()` that uses the `Default` trait * add `Default` implementations for vecs, HashMap, Option * add `Option.and(T) -> Option<T>`, `Option.and_then(&fn() -> Option<T>) -> Option<T>`, `Option.or(T) -> Option<T>`, and `Option.or_else(&fn() -> Option<T>) -> Option<T>` * add `option::ToOption`, `option::IntoOption`, `option::AsOption`, `result::ToResult`, `result::IntoResult`, `result::AsResult`, `either::ToEither`, and `either::IntoEither`, `either::AsEither` * renamed `Option::chain*` and `Result::chain*` to `and_then` and `or_else` to avoid the eventual collision with `Iterator.chain`. * Added a bunch of impls of `Default` * Added a `#[deriving(Default)]` syntax extension * Removed impls of `Zero` for `Option<T>` and vecs.
-
由 bors 提交于
While usage of change_dir_locked is synchronized against itself, it's not synchronized against other relative path usage, so I'm of the opinion that it just really doesn't help in running tests. In order to prevent the problems that have been cropping up, this completely removes the function. All existing tests (except one) using it have been moved to run-pass tests where they get their own process and don't need to be synchronized with anyone else. There is one now-ignored rustpkg test because when I moved it to a run-pass test apparently run-pass isn't set up to have 'extern mod rustc' (it ends up having linkage failures).
-