- 26 10月, 2018 2 次提交
-
-
由 Nick Cameron 提交于
Requires adding path segments to the hir map
-
由 Nick Cameron 提交于
-
- 23 10月, 2018 3 次提交
-
-
由 Matthias Krüger 提交于
-
由 Shotaro Yamada 提交于
-
由 Esteban Küber 提交于
Suggest using `'static` when a lifetime is missing in the return type with a structured suggestion instead of a note.
-
- 20 10月, 2018 1 次提交
-
-
由 Scott McMurray 提交于
It's already stable in 2018; this finishes the stabilization.
-
- 19 10月, 2018 3 次提交
-
-
由 Oliver Scherer 提交于
-
由 Oliver Scherer 提交于
-
由 ljedrz 提交于
-
- 18 10月, 2018 1 次提交
-
-
由 Niko Matsakis 提交于
-
- 14 10月, 2018 1 次提交
-
-
由 ljedrz 提交于
-
- 12 10月, 2018 2 次提交
-
-
由 Niko Matsakis 提交于
-
由 David Wood 提交于
This commit extends the existing lang items functionality to assert that the `#[lang_item]` attribute is only found on the appropriate item for any given lang item. That is, language items representing traits must only ever have their corresponding attribute placed on a trait, for example.
-
- 10 10月, 2018 1 次提交
-
-
由 Esteban Küber 提交于
-
- 07 10月, 2018 1 次提交
-
-
由 Alex Crichton 提交于
This commit updates the compiler to allow the `#[no_mangle]` (and `#[export_name]` attributes) to be located anywhere within a crate. These attributes are unconditionally processed, causing the compiler to always generate an exported symbol with the appropriate name. After some discussion on #54135 it was found that not a great reason this hasn't been allowed already, and it seems to match the behavior that many expect! Previously the compiler would only export a `#[no_mangle]` symbol if it were *publicly reachable*, meaning that it itself is `pub` and it's otherwise publicly reachable from the root of the crate. This new definition is that `#[no_mangle]` *is always reachable*, no matter where it is in a crate or whether it has `pub` or not. This should make it much easier to declare an exported symbol with a known and unique name, even when it's an internal implementation detail of the crate itself. Note that these symbols will persist beyond LTO as well, always making their way to the linker. Along the way this commit removes the `private_no_mangle_functions` lint (also for statics) as there's no longer any need to lint these situations. Furthermore a good number of tests were updated now that symbol visibility has been changed. Closes #54135
-
- 05 10月, 2018 1 次提交
-
-
由 Vadim Petrochenkov 提交于
-
- 04 10月, 2018 1 次提交
-
-
由 varkor 提交于
-
- 03 10月, 2018 1 次提交
-
-
由 varkor 提交于
-
- 02 10月, 2018 2 次提交
-
-
由 Oliver Schneider 提交于
-
由 David Wood 提交于
This commit adds an `ImplicitSelfKind` to the HIR and the MIR that keeps track of whether a implicit self argument is immutable by-value, mutable by-value, immutable reference or mutable reference so that the addition of the `mut` keyword can be suggested for the immutable by-value case.
-
- 01 10月, 2018 1 次提交
-
-
由 Alexander Regueiro 提交于
-
- 30 9月, 2018 1 次提交
-
-
由 Zack M. Davis 提交于
This seemed like a good way to kick the tires on the elided-lifetimes-in-paths lint (#52069)—seems to work! This was also pretty tedious—it sure would be nice if `cargo fix` worked on this codebase (#53896)!
-
- 26 9月, 2018 1 次提交
-
-
由 ljedrz 提交于
-
- 25 9月, 2018 3 次提交
-
-
由 Alexander Regueiro 提交于
-
由 Matthew Jasper 提交于
-
由 Alexander Regueiro 提交于
-
- 22 9月, 2018 1 次提交
-
-
由 Scott McMurray 提交于
(While still prohibiting explicit and in-band in the same header.)
-
- 21 9月, 2018 1 次提交
-
-
由 Keith Yeung 提交于
-
- 20 9月, 2018 3 次提交
-
-
由 QuietMisdreavus 提交于
-
由 Scott McMurray 提交于
- Check for valid attributes more reliably - Don't bloat the error index for boring errors - Do use real error codes for the interesting ones
-
由 Scott McMurray 提交于
-
- 19 9月, 2018 1 次提交
-
-
由 Diogo Sousa 提交于
Before this two macros with same name would be indistinguishable inside a `FileName`. This caused a bug in incremental compilation (see #53097) since two different macros would map out to the same `StableFilemapId`. Fixes #53097.
-
- 13 9月, 2018 1 次提交
-
-
由 F001 提交于
-
- 12 9月, 2018 1 次提交
-
-
由 ljedrz 提交于
-
- 11 9月, 2018 2 次提交
-
-
由 Oliver Schneider 提交于
-
由 Oliver Schneider 提交于
-
- 07 9月, 2018 4 次提交
-
-
由 Niko Matsakis 提交于
Also, adjust the MAX to be `u32::MAX - 1`, leaving room for `u32::MAX` to become a sentinel value in the future.
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
-
由 Niko Matsakis 提交于
-