- 26 1月, 2016 2 次提交
-
-
由 Corey Farwell 提交于
-
由 bors 提交于
Also got rid of some code repetition in `const_eval`
-
- 25 1月, 2016 9 次提交
-
-
由 bors 提交于
Register LLVM passes with the correct LLVM pass manager. LLVM was upgraded to a new version in this commit: https://github.com/rust-lang/rust/commit/f9d4149c29e8b989fa3624993be379f380e48dcf which was part of this pull request: https://github.com/rust-lang/rust/issues/26025 Consider the following two lines from that commit: https://github.com/rust-lang/rust/commit/f9d4149c29e8b989fa3624993be379f380e48dcf#diff-a3b24dbe2ea7c1981f9ac79f9745f40aL462 https://github.com/rust-lang/rust/commit/f9d4149c29e8b989fa3624993be379f380e48dcf#diff-a3b24dbe2ea7c1981f9ac79f9745f40aL469 The purpose of these lines is to register LLVM passes. Prior to the that commit, the passes being handled were assumed to be ModulePasses (a specific type of LLVM pass) since they were being added to a ModulePass manager. After that commit, both lines were refactored (presumably in an attempt to DRY out the code), but the ModulePasses were changed to be registered to a FunctionPass manager. This change resulted in ModulePasses being run, but a Function object was being passed as a parameter to the pass instead of a Module, which resulted in segmentation faults. In this commit, I changed relevant sections of the code to check the type of the passes being added and register them to the appropriate pass manager. Closes https://github.com/rust-lang/rust/issues/31067
-
由 Adrian Heine 提交于
In 95d90462 output was accidentally moved from STDERR to STDOUT. This commit also changes the order of debug output. Previously, it was: ``` /* id 22: … */ { … } DEBUG:rustc::middle::dataflow: ``` Now, it is: ``` DEBUG:rustc::middle::dataflow: /* id 22: … */ { … } ```
-
由 Corey Farwell 提交于
LLVM was upgraded to a new version in this commit: https://github.com/rust-lang/rust/commit/f9d4149c29e8b989fa3624993be379f380e48dcf which was part of this pull request: https://github.com/rust-lang/rust/issues/26025 Consider the following two lines from that commit: https://github.com/rust-lang/rust/commit/f9d4149c29e8b989fa3624993be379f380e48dcf#diff-a3b24dbe2ea7c1981f9ac79f9745f40aL462 https://github.com/rust-lang/rust/commit/f9d4149c29e8b989fa3624993be379f380e48dcf#diff-a3b24dbe2ea7c1981f9ac79f9745f40aL469 The purpose of these lines is to register LLVM passes. Prior to the that commit, the passes being handled were assumed to be ModulePasses (a specific type of LLVM pass) since they were being added to a ModulePass manager. After that commit, both lines were refactored (presumably in an attempt to DRY out the code), but the ModulePasses were changed to be registered to a FunctionPass manager. This change resulted in ModulePasses being run, but a Function object was being passed as a parameter to the pass instead of a Module, which resulted in segmentation faults. In this commit, I changed relevant sections of the code to check the type of the passes being added and register them to the appropriate pass manager. Closes https://github.com/rust-lang/rust/issues/31067
-
由 bors 提交于
Also remove a "finally" in the section about building for release to make it feel a bit friendlier.
-
由 bors 提交于
-
由 bors 提交于
Version of Clang in repository is 3.9 So, error is caused by ``` ./configure --enable-dist-host-only --enable-clang ``` Then, I got ``` configure: error: bad CLANG version: 3.9.0 (http://llvm.org/git/clang.git 3d5d4c39659f11dfbe8e11c857cadf5c449b559b) (http://llvm.org/git/llvm.git, need >=3.0svn ``` I fixed this issue by appending 3.9* in the if sentence. Thanks.
-
由 Geoffrey Thomas 提交于
The implementation changed in 33a2191d, but the comments did not change to match.
- 24 1月, 2016 6 次提交
-
-
由 bors 提交于
Fixes #30705 r? @nagisa
-
由 Ariel Ben-Yehuda 提交于
Fixes #30705
-
由 mopp 提交于
-
由 Tshepang Lekhonkhobe 提交于
-
由 Dirk Gadsden 提交于
Also remove a "finally" in the section about building for release to make it feel a bit friendlier.
-
由 bors 提交于
- Successful merges: #30997, #31019, #31031, #31035, #31045, #31050, #31054, #31055, #31061, #31088, #31090, #31111, #31113, #31128, #31130, #31136, #31145, #31146 - Failed merges: #30932
-
- 23 1月, 2016 23 次提交
-
-
由 Steve Klabnik 提交于
-
由 Steve Klabnik 提交于
r? @steveklabnik
-
由 Steve Klabnik 提交于
Also change the examples to make this more obvious. Fixes #31129.
-
由 Steve Klabnik 提交于
E0210 explains about orphan rules and suggests using a local type as a workaround. It wasn't obvious to me that I couldn't use a type alias, so I added a note.
-
由 Steve Klabnik 提交于
-
由 Steve Klabnik 提交于
r? @alexcrichton
-
由 Steve Klabnik 提交于
Closes #31103 r? @steveklabnik
-
由 Steve Klabnik 提交于
-
由 Steve Klabnik 提交于
-
由 Steve Klabnik 提交于
-
由 Steve Klabnik 提交于
-
由 Steve Klabnik 提交于
I've been interested in the accessibility of Rustdoc's output, but never did anything about it. Today, I ran a tool, and it suggested adjusting some colors. Here's some screen shots. Before: ![2016-01-20-114944_443x199_scrot](https://cloud.githubusercontent.com/assets/27786/12455979/d84d7ae8-bf6b-11e5-9aea-0602fb1a8cfa.png) After: ![2016-01-20-114516_453x204_scrot](https://cloud.githubusercontent.com/assets/27786/12455841/36a55d14-bf6b-11e5-8014-239594c12e46.png) As you can see, the link text is just a _shade_ darker. Browsable: http://www.steveklabnik.com/rust-a11y-doc-testing/doc/std/
-
由 Steve Klabnik 提交于
Closes #31048 r? @Manishearth
-
由 Steve Klabnik 提交于
I tried to add an inline `span_suggestion()` to the error as well, but since generics don't have their own span it becomes too fragile/complicated to work. r? @steveklabnik fixes #19477
-
由 Steve Klabnik 提交于
Responding to [a thread of discussion on the Rust subreddit](https://www.reddit.com/r/rust/comments/3racik/mutable_lifetimes_are_too_long_when_matching_an/), it was identified that the presence of the Entry API is not duly publicised. This commit aims to add some reasonable examples of common usages of this API to the main example secion of the `HashMap` documentation. This is part of issue #29348.
-
由 Steve Klabnik 提交于
This was fixed in passing. Adding a regression test.
-
由 Steve Klabnik 提交于
Documentation of `CStr::from_ptr` suggests using `str::from_utf8(slice.to_bytes()).unwrap()` to obtain a `&str` but `CStr` has `CStr::to_str` that does exactly that. (First PR, be nice :)
-
由 Steve Klabnik 提交于
Fix type parameter default error to mention type and trait definitions Introduced in PR #30724, needs to mention that type parameter defaults are legal in trait and type definitions too.
-
由 bors 提交于
Fix type parameter default error to mention type and trait definitions Introduced in PR #30724, needs to mention that type parameter defaults are legal in trait and type definitions too.
-
由 angelsl 提交于
-
由 bors 提交于
We currently nest `<a>` tags which is doubleplusungood. So, for example, `(u8, u8)` will show up with the left paren linked to the tuple primitive page, and the right paren unlinked, which looks ugly.
-
由 Manish Goregaokar 提交于
-
由 bors 提交于
The COPYRIGHT file should be updated to note that Rust no longer ships with AUTHORS.txt. $ git log -1 -- AUTHORS.txt commit 402749c5 Author: Brian Anderson <banderson@mozilla.com> Date: Wed Dec 2 22:16:08 2015 +0000 Remove AUTHORS.txt and add-authors.sh Keeping this file up to date requires hours of work every release, even with the script. It is a fool's errand and we shall not do it any longer.
-