- 01 3月, 2018 2 次提交
-
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
Always using root environment for now.
-
- 23 2月, 2018 2 次提交
-
-
由 varkor 提交于
This adds an `UnpackedKind` type as a typesafe counterpart to `Kind`. This should make future changes to kinds (such as const generics!) more resilient, as the type-checker should catch more potential issues.
-
由 Niko Matsakis 提交于
Fixes #46688.
-
- 21 2月, 2018 1 次提交
-
-
由 Esteban Küber 提交于
-
- 20 2月, 2018 1 次提交
-
-
由 Mark Simulacrum 提交于
-
- 18 2月, 2018 1 次提交
-
-
由 csmoe 提交于
-
- 15 2月, 2018 1 次提交
-
-
由 Gianni Ciccarelli 提交于
-
- 14 2月, 2018 2 次提交
-
-
由 csmoe 提交于
-
由 bobtwinkles 提交于
We need two-phase borrows of ops to be in the initial NLL release since without them lots of existing code will break. Fixes #48129
-
- 13 2月, 2018 2 次提交
-
-
由 Niko Matsakis 提交于
Instead of creating inference variables for those argument types, use the trait error-reporting code to give a nicer error.
-
由 Niko Matsakis 提交于
-
- 10 2月, 2018 1 次提交
-
-
由 Gianni Ciccarelli 提交于
-
- 09 2月, 2018 2 次提交
-
-
由 Alex Crichton 提交于
This commit disallows acquiring a function pointer to functions tagged as `#[rustc_args_required_const]`. This is intended to be used as future-proofing for the stdsimd crate to avoid taking a function pointer to any intrinsic which has a hard requirement that one of the arguments is a constant value.
-
由 leonardo.yvens 提交于
This turns out to not be backwards compatible.
-
- 08 2月, 2018 5 次提交
-
-
由 Felix S. Klock II 提交于
Namely, the mutable borrows also carries a flag indicating whether they should support two-phase borrows. This allows us to thread down, from the point of the borrow's introduction, whether the particular adjustment that created it is one that yields two-phase mutable borrows.
-
由 Esteban Küber 提交于
Add extra inline documentation to E0019, E0016, E0013, E0396, E0017, E0018, E0010, E0022, E0030, E0029, E0033, E0026 and E0027.
-
由 Gianni Ciccarelli 提交于
not skipping any wfchecks on default impls
-
由 Gianni Ciccarelli 提交于
a default impl should never be considered as implementing the trait on its own -- regardless of whether it contains all items or not
-
由 Gianni Ciccarelli 提交于
a `default impl` need not include all items from the trait a `default impl` alone does not mean that a type implements the trait
-
- 07 2月, 2018 1 次提交
-
-
由 Manish Goregaokar 提交于
-
- 06 2月, 2018 5 次提交
-
-
由 Ralf Jung 提交于
-
由 Manish Goregaokar 提交于
-
由 Zack M. Davis 提交于
Previously, when the type of a method receiver could not be determined, the error message would, potentially confusingly, highlight the span of the entire method call. Resolves #36598, resolves #42234.
-
由 Ralf Jung 提交于
-
由 Ralf Jung 提交于
-
- 01 2月, 2018 1 次提交
-
-
由 Eduard-Mihai Burtescu 提交于
-
- 31 1月, 2018 2 次提交
-
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
-
- 29 1月, 2018 8 次提交
-
-
由 John Kåre Alsaker 提交于
-
由 John Kåre Alsaker 提交于
-
由 Esteban Küber 提交于
- On mismatch between impl and trait method, point at the trait signature. - Point only at the method signature instead of the whole body on trait/impl mismatch errors.
-
由 Eduard-Mihai Burtescu 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
由 Eduard-Mihai Burtescu 提交于
-
- 28 1月, 2018 3 次提交
-
-
由 leonardo.yvens 提交于
-
由 leonardo.yvens 提交于
Move `check_casts` and `resolve_generator_interiors` to before fallback. Rename `apply_fallback_if_possible` to `fallback_if_possible`. Refactor `select_all_obligations_or_error`.
-
由 leonardo.yvens 提交于
-