- 18 5月, 2013 1 次提交
-
-
由 bors 提交于
-
- 17 5月, 2013 33 次提交
-
-
由 Huon Wilson 提交于
-
由 bors 提交于
Added unit test to prevent similar mistakes from happening again. The previous method was wrong because it dereferenced a pointer to a void type to match on the result. No self pointer was needed, and the correct method signature took the self value by value. I feel silly that I made this mistake in https://github.com/mozilla/rust/pull/6348
-
由 bors 提交于
-
由 bors 提交于
This closes #6548 The change makes it match the standard Load signature.
-
由 bors 提交于
As discussed on issue #4819. This is a naive implementation, trusting LLVM to do the relevant optimizations. In the future this could be implemented more efficiently, but it's a start.
-
由 bors 提交于
Closes #2647 This way it's much easier to add lints throughout compilation correctly, and functions on impls can alter the way lints are emitted. This involved pretty much rewriting how lints are emitted. Beforehand, only items could alter the lint settings, so whenever a lint was added it had to be associated with whatever item id it was coming from. I removed this (possibly questionably) in favor of just specifying a span and a message when adding a lint. When lint checking comes around, it looks at all the lints and sees which node with attributes best encloses it and uses that level of linting. This means that all consumer code doesn't have to deal with what item things came from (especially because functions on impls aren't items). More details of this can be found in the code (and comments). As a bonus, I managed to greatly simplify emission of lints in resolve.rs about unused imports. Now instead of it manually tracking what the lint level is, it's all moved over into the lint module (as is to be expected).
-
由 Alex Crichton 提交于
-
由 Alex Crichton 提交于
Achieves ~3x speedup on lint passes for libcore
-
由 Alex Crichton 提交于
This way it's much easier to add lints throughout compilation correctly, and functions on impls can alter the way lints are emitted.
-
由 bors 提交于
-
由 bors 提交于
Closes #5127
-
由 Corey Richardson 提交于
-
由 James Miller 提交于
-
由 Brendan Zabarauskas 提交于
-
由 Corey Richardson 提交于
-
由 bors 提交于
-
由 Corey Richardson 提交于
-
由 Daniel Micay 提交于
-
由 Corey Richardson 提交于
-
由 Tommy M. McGuire 提交于
-
由 Tommy M. McGuire 提交于
-
由 bors 提交于
-
由 Tim Chevalier 提交于
-
由 Tim Chevalier 提交于
-
由 bors 提交于
r? @nikomatsakis Impls can implement either zero or one traits; this has been true more or less since we removed classes. So I got rid of the comments saying "we should support multiple traits" and changed the code to make it clear that we don't. This is just cleanup, and doesn't break any existing tests.
-
由 Tim Chevalier 提交于
Impls can implement either zero or one traits; this has been true more or less since we removed classes. So I got rid of the comments saying "we should support multiple traits" and changed the code to make it clear that we don't. This is just cleanup, and doesn't break any existing tests.
-
由 bors 提交于
-
由 bors 提交于
Simpler version of PR #5974 based on new borrowck.
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
-
由 Brian Anderson 提交于
-
由 bors 提交于
Add BuiltinBounds to closure type: parse and handle subtyping, but do not integrate with kindck etc (requires a snapshot first) r? @brson
-
由 Niko Matsakis 提交于
but do not integrate with kindck etc (requires a snapshot first)
-
- 16 5月, 2013 6 次提交
-
-
由 bors 提交于
-
由 Huon Wilson 提交于
-
由 bors 提交于
Fix #4334.
-
由 Huon Wilson 提交于
-
由 bors 提交于
This is still enough to prevent cycles (explanation given in the docstring).
-
由 kud1ing 提交于
-