- 07 1月, 2018 1 次提交
-
-
由 Robin Kruppe 提交于
The `#[simd]` attribute has been deprecated since c8b6d5b2 back in 2015. Any nightly crates using it have had ample time to switch to `#[repr(simd)]`, and if they didn't they're likely broken by now anyway.
-
- 04 1月, 2018 1 次提交
-
-
由 Eduard-Mihai Burtescu 提交于
-
- 01 1月, 2018 1 次提交
-
-
由 Malo Jaffré 提交于
-
- 28 12月, 2017 1 次提交
-
-
由 Seiichi Uchida 提交于
-
- 22 12月, 2017 1 次提交
-
-
由 John Kåre Alsaker 提交于
-
- 20 12月, 2017 1 次提交
-
-
由 Michael Woerister 提交于
-
- 18 12月, 2017 4 次提交
-
-
由 Maik Klein 提交于
-
由 Maik Klein 提交于
-
由 Maik Klein 提交于
-
由 Maik Klein 提交于
-
- 15 12月, 2017 2 次提交
-
-
由 Niko Matsakis 提交于
The existing flags did not consider `'static` to be "free". This then fed into what was "erasable" -- but `'static` is most certainly erasable.
-
由 Alex Burka 提交于
-
- 14 12月, 2017 1 次提交
-
-
由 Ariel Ben-Yehuda 提交于
Nested generics (aka method generics) in trait methods don't have an *additional* Self parameter in their own type parameter list (they have a Self parameter in the parent generics), so don't try to check we're correctly adjusting for it. Fixes #46568.
-
- 06 12月, 2017 2 次提交
-
-
由 Oliver Schneider 提交于
-
由 Jeffrey Seyfried 提交于
-
- 04 12月, 2017 1 次提交
-
-
由 Niko Matsakis 提交于
Previously the code was somewhat duplicated.
-
- 29 11月, 2017 1 次提交
-
-
由 Michael Woerister 提交于
-
- 28 11月, 2017 1 次提交
-
-
由 Michael Woerister 提交于
-
- 19 11月, 2017 2 次提交
-
-
由 Eduard-Mihai Burtescu 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
- 18 11月, 2017 3 次提交
-
-
由 Niko Matsakis 提交于
The closure kinds themselves are now completely found in the `ClosureSubsts`.
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
Similar to how freshen handled things, but "always happening"; we can thus remove the corresponding code from `freshen`.
-
- 16 11月, 2017 4 次提交
-
-
由 Michael Woerister 提交于
-
由 Michael Woerister 提交于
-
由 Niko Matsakis 提交于
Instead, just search the param env predicates directly. This is equivalent to what we were doing before but more efficient.
-
由 Niko Matsakis 提交于
This new way is **slightly** less expressive (I would be shocked if it affects any code, though) when it comes to higher-ranked bounds or a few other weird tricks. But we don't handle those consistently regardless, and the new way does not require normalization and is just wildly simpler.
-
- 13 11月, 2017 1 次提交
-
-
由 Eduard-Mihai Burtescu 提交于
-
- 04 11月, 2017 3 次提交
-
-
由 David Wood 提交于
-
由 leonardo.yvens 提交于
-
由 leonardo.yvens 提交于
DefaultImpl is a highly confusing name for what we now call auto impls, as in `impl Send for ..`. The name auto impl is not formally decided but for sanity anything is better than `DefaultImpl` which refers neither to `default impl` nor to `impl Default`.
-
- 28 10月, 2017 1 次提交
-
-
由 Paul Lietar 提交于
-
- 24 10月, 2017 4 次提交
-
-
由 Igor Matuszewski 提交于
-
由 Michael Woerister 提交于
-
由 Simon Sapin 提交于
This custom tracking is now replaced by the red/green algorithm. Fix https://github.com/rust-lang/rust/issues/45471
-
由 Igor Matuszewski 提交于
-
- 17 10月, 2017 2 次提交
-
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
The cache was broken anyhow and this computation doesn't look that expensive. These public accessors could potentially become queries, but we'd have to add some more complex logic around lift. I'd prefer to have some test cases to profile with before doing that. Fixes #44402.
-
- 06 10月, 2017 1 次提交
-
-
由 Vadim Petrochenkov 提交于
-
- 02 10月, 2017 1 次提交
-
-
由 Michael Woerister 提交于
-