- 25 11月, 2015 1 次提交
-
-
由 Steve Klabnik 提交于
Part of https://github.com/rust-lang/rust/issues/29333
-
- 24 11月, 2015 1 次提交
-
-
由 bors 提交于
Replace `TypeNsDef` and `ValueNsDef` with a more general type `NsDef`. Define a newtype `NameBinding` for `Rc<RefCell<Option<NsDef>>>` and refactor `NameBindings` to be a `NameBinding` for each namespace. Replace uses of `NameBindings` with `NameBinding` where only one binding is being used (in `NamespaceResult`, `Target,` etc). Refactor away `resolve_definition_of_name_in_module` and `NameDefinition`, fixing issue #4952.
-
- 23 11月, 2015 9 次提交
-
-
由 bors 提交于
-
由 Philipp Matthias Schäfer 提交于
-
由 bors 提交于
I'd like to have the message print out the index and length values like it does elsewhere, but I'm not sure how to do that without affecting perf here. Will `assert!(cond, "index out of bounds got {} but len is ", idx, len)` make things slower? It calls `panic_fmt` which is marked as cold but also calls `format_args!`, and I don't know if that allocates or does any heavy lifting. cc @alexcrichton @Gankro
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
-
由 bors 提交于
Hey hey, This is the result of running rustfmt over the libterm module. The first commit reflects the unaltered changes from rustfmt, and the commit message contains some notes on areas where I thought rustfmt had behaved strangely. The second commit attempts to fix the strange areas from the first commit. Clarification edit: there are still some areas where I think rustfmt has made changes which may merit discussion (one is noted in the comments below). My second commit only undoes the changes that I figured would not warrant discussion (based on my opinion of the style, which is of course subjective). r? @nrc
-
由 bors 提交于
Includes rust-lang-nursery/libc#66 which should: Closes #29818 Closes #29956
-
由 Alex Crichton 提交于
Includes rust-lang-nursery/libc#66 which should: Closes #29956
-
由 bors 提交于
Fixes #29972.
-
- 22 11月, 2015 9 次提交
-
-
由 Tobias Bucher 提交于
Fixes #29972.
-
由 bors 提交于
r? @Gankro
-
由 bors 提交于
None
-
由 Manish Goregaokar 提交于
fixes #29922
-
由 Manish Goregaokar 提交于
fixes #29665
-
由 Manish Goregaokar 提交于
fixes #5780
-
由 Bryce Van Dyk 提交于
-
由 bors 提交于
Since fat pointers do not qualify as structural types, they got copied using load_ty and store_ty, which means that we load an FCA and use extractvalue to get the components of the fat pointer. This breaks certain optimizations in LLVM. Found via apasel422/ref_count#13
-
- 21 11月, 2015 11 次提交
-
-
由 bors 提交于
This commit changes the location of the rust docs. https://github.com/rust-lang/rust/commit/024aa9a345e92aa1926517c4d9b16bd83e74c10d Clicking the contribution link on the front page therefore becomes a 'not found' error.
-
由 bors 提交于
Implement #29919
-
由 bors 提交于
On Windows: Previously these paths were silently truncated at these NUL characters, now they fail with `ErrorKind::InvalidInput`.
-
由 Tobias Bucher 提交于
This check is necessary, because the underlying API only reads strings until the first NUL.
-
由 bors 提交于
None
-
由 Matthias Kauer 提交于
-
由 bors 提交于
This commit fixes a bug where a crate could fail to compile depending on the order of `extern crate` directives at the top of the crate. Specifically, if the same crate is found at two locations, then if it's loaded first via `--extern` it will not emit a duplicate warning, but if it's first loaded transitively via a dep and *then* via `--extern` an error will be emitted. The loader was tweaked to catch this scenario and coalesce the loading of these two crates to prevent errors from being emitted.
-
由 Björn Steinbrink 提交于
Since fat pointers do not qualify as structural types, they got copied using load_ty and store_ty, which means that we load an FCA and use extractvalue to get the components of the fat pointer. This breaks certain optimizations in LLVM. Found via apasel422/ref_count#13
-
由 bors 提交于
r? @alexcrichton This prevents outputting csv files with the same name and thus overwriting each other when indexing Cargo projects with a bin crate (and some other cases).
-
由 Alex Crichton 提交于
This commit fixes a bug where a crate could fail to compile depending on the order of `extern crate` directives at the top of the crate. Specifically, if the same crate is found at two locations, then if it's loaded first via `--extern` it will not emit a duplicate warning, but if it's first loaded transitively via a dep and *then* via `--extern` an error will be emitted. The loader was tweaked to catch this scenario and coalesce the loading of these two crates to prevent errors from being emitted.
-
由 bors 提交于
This patch implements the plan described in https://internals.rust-lang.org/t/privacy-and-its-interaction-with-docs-lints-and-stability/2880 with one deviation. It turns out, that rustdoc needs the "directly public" set for its docs inlining logic, so the privacy pass have to produce three sets and not two. Three is arguably too many, so I merged them in one map: `public_items/exported_items/reachable_items: NodeSet => access_levels: NodeMap<AccessLevel>` r? @alexcrichton
-
- 20 11月, 2015 9 次提交
-
-
由 Manish Goregaokar 提交于
-
由 bors 提交于
PR for #29930. Adds missing #![feature(slice_patterns)] to make compiler plugin example compile again.
-
由 Florian Hahn 提交于
closes #29930
-
由 bors 提交于
This tiny PR renames the result variable in HashSet's `intersection` example from `diff` to `intersection` and the same for `union`, which seem more appropriate.
-
由 Florian Hahn 提交于
-
由 bors 提交于
-
由 Devon Hollowood 提交于
-
由 bors 提交于
Corresponds directly to llvm's inline-threshold. I want this so I can experiment out-of-tree with tweaking optimization settings, and this is the most important value that isn't exposed. I can't get it to work either via `-C llvm-args`. cc @rust-lang/compiler
-
由 bors 提交于
-