about summary refs log tree commit diff
path: root/src/test/ui/feature-gates
AgeCommit message (Collapse)AuthorLines
2018-12-27Make sure feature gate errors are recoverableVadim Petrochenkov-8/+18
2018-12-27Do not abort compilation if expansion produces errorsVadim Petrochenkov-3/+5
Fix a number of uncovered deficiencies in diagnostics
2018-12-26Fixed issues raised in first review.Alexander Regueiro-46/+4
2018-12-26Fixed tests.Alexander Regueiro-10/+18
2018-12-26Added tests for feature.Alexander Regueiro-0/+97
2018-12-25Remove licensesMark Rousskov-1655/+358
2018-12-23Rollup merge of #57049 - cramertj:repr-packed, r=Centrilkennytm-37/+0
Stabilize #[repr(packed(N))] Fixes https://github.com/rust-lang/rust/issues/33158
2018-12-21Stabilize #[repr(packed(N))]Taylor Cramer-37/+0
2018-12-20Stabilize `Rc`, `Arc` and `Pin` as method receiversMichael Hewson-22/+34
This lets you write methods using `self: Rc<Self>`, `self: Arc<Self>`, `self: Pin<&mut Self>`, `self: Pin<Box<Self>`, and other combinations involving `Pin` and another stdlib receiver type, without needing the `arbitrary_self_types`. Other user-created receiver types can be used, but they still require the feature flag to use. This is implemented by introducing a new trait, `Receiver`, which the method receiver's type must implement if the `arbitrary_self_types` feature is not enabled. To keep composed receiver types such as `&Arc<Self>` unstable, the receiver type is also required to implement `Deref<Target=Self>` when the feature flag is not enabled. This lets you use `self: Rc<Self>` and `self: Arc<Self>` in stable Rust, which was not allowed previously. It was agreed that they would be stabilized in #55786. `self: Pin<&Self>` and other pinned receiver types do not require the `arbitrary_self_types` feature, but they cannot be used on stable because `Pin` still requires the `pin` feature.
2018-12-18Auto merge of #56160 - oli-obk:const_fn_let, r=nikomatsakisbors-8/+89
Fix various aspects around `let` bindings inside const functions * forbid `let` bindings in const contexts that use short circuiting operators * harden analysis code against derefs of mutable references Initially this PR was about stabilizing `let` bindings, but too many flaws were exposed that need some more testing on nightly
2018-12-17Stabilize `underscore_imports`Vadim Petrochenkov-33/+0
2018-12-14Auto merge of #56351 - davidtwco:issue-55396-stabilize-linker-flavor, r=nagisabors-28/+0
Stabilize `linker-flavor` flag. Part of #55396. This commit moves the linker-flavor flag from a debugging option to a codegen option, thus stabilizing it. There are no feature flags associated with this flag. r? @nagisa
2018-12-13Stabilize `linker-flavor` flag.David Wood-28/+0
This commit moves the linker-flavor flag from a debugging option to a codegen option, thus stabilizing it. There are no feature flags associated with this flag.
2018-12-07Unsupport `#[derive(Trait)]` sugar for `#[derive_Trait]` legacy plugin ↵Vadim Petrochenkov-26/+0
attributes
2018-12-06Auto merge of #56392 - petrochenkov:regensym, r=oli-obkbors-15/+27
Delay gensym creation for "underscore items" (`use foo as _`/`const _`) until name resolution So they cannot be cloned by macros. See https://github.com/rust-lang/rust/pull/56303 for the discussion. Mostly fix cross-crate use of underscore items by inverting the "gensyms are lost in metadata" bug as described in https://github.com/rust-lang/rust/pull/56303#issuecomment-442464695. Fix unused import warnings for single-segment imports (first commit) and `use crate_name as _` imports (as specified in https://github.com/rust-lang/rust/pull/56303#issuecomment-442274118). Prohibit accidentally implemented `static _: TYPE = EXPR;` (cc https://github.com/rust-lang/rust/pull/55983). Add more tests for `use foo as _` imports.
2018-12-06Rollup merge of #56362 - varkor:stabilise-exhaustive-integer-patterns, ↵Pietro Albini-0/+29
r=nikomatsakis Stabilise exhaustive integer patterns This is dependent on the FCP for https://github.com/rust-lang/rfcs/pull/2591 being completed, but that should happen tomorrow, so there's little harm in opening this PR early. Closes #50907.
2018-12-04Update testsOliver Scherer-2/+10
2018-12-03Rollup merge of #56412 - petrochenkov:extself, r=Centrilkennytm-1/+1
Update tracking issue for `extern_crate_self`
2018-12-03Rollup merge of #56366 - alexreg:stabilise-self_in_typedefs, r=Centrilkennytm-29/+0
Stabilize self_in_typedefs feature [**Tracking Issue**](https://github.com/rust-lang/rust/issues/49303) r? @centril
2018-12-02Delay gensym creation for "underscore items" until name resolutionVadim Petrochenkov-0/+24
Prohibit `static _` Fis unused import warnings for `use foo as _` Add more tests for `use foo as _`
2018-12-02resolve: Avoid "self-confirming" resolutions in import validationVadim Petrochenkov-15/+3
2018-12-01Update tracking issue for `extern_crate_self`Vadim Petrochenkov-1/+1
2018-12-01resolve: Support aliasing local crate root in extern preludeVadim Petrochenkov-0/+14
2018-11-30Removed feature gate.Alexander Regueiro-29/+0
2018-12-01Rollup merge of #56365 - alexreg:stabilise-self_struct_ctor, r=Centrilkennytm-41/+0
Stabilize self_struct_ctor feature. [**Tracking Issue**](https://github.com/rust-lang/rust/issues/51994)
2018-11-30Moved feature-gate tests to correct dir.Alexander Regueiro-0/+118
2018-11-30Removed feature gate.Alexander Regueiro-41/+0
2018-11-30Add precise_pointer_size_matching featurevarkor-0/+29
2018-11-30Reenable `const_let` feature gateOliver Scherer-0/+31
2018-11-30Allow `let` bindings everywhereOliver Scherer-31/+0
2018-11-30Also test the `const_let` feature gate in staticsOliver Scherer-1/+54
2018-11-30Stabilize `const_let` inside const functionsOliver Scherer-9/+37
2018-11-21Stabilize macro_literal_matcherDan Aloni-30/+0
2018-11-21Stabilize `extern_crate_item_prelude`Vadim Petrochenkov-121/+0
2018-11-18resolve: Avoid sentence breaks in diagnosticsVadim Petrochenkov-3/+3
2018-11-18resolve: Reintroduce feature gate for uniform paths in importsVadim Petrochenkov-8/+68
2018-11-18resolve: Resolve single-segment imports using in-scope resolution on 2018 ↵Vadim Petrochenkov-3/+3
edition
2018-11-08Auto merge of #55532 - pnkfelix:rustc_error-survey, r=nikomatsakisbors-2/+2
#[rustc_error] survey Fix #55505
2018-11-07remove `#[rustc_error]` from ui/ tests that remain compile-fail tests.Felix S. Klock II-2/+2
2018-11-07Rollup merge of #55510 - bitshifter:repr-feature-gate-fix, r=petrochenkovkennytm-2/+26
Fix feature gate only being checked on first repr attr. Reported in https://github.com/rust-lang/rust/issues/33158#issuecomment-412185357.
2018-11-06Rollup merge of #55700 - pnkfelix:issue-55533-update-ui-tests-wrt-nll, ↵kennytm-24/+11
r=davidtwco Update ui tests with respect to NLL Fix #55533
2018-11-06Rollup merge of #55601 - petrochenkov:featissue, r=pnkfelixkennytm-44/+12
Fix tracking issue numbers for some unstable features And also remove deprecated unstable `#[panic_implementation]` attribute that was superseded by stable `#[panic_handler]` and doesn't have an open tracking issue.
2018-11-05Auto merge of #55410 - nagisa:atomic-align, r=pnkfelixbors-7/+43
Correct alignment of atomic types and (re)add Atomic{I,U}128 This is a updated https://github.com/rust-lang/rust/pull/53514 to also make atomic types `repr(C)` as per comment in https://github.com/rust-lang/rust/pull/53514#issuecomment-431042767. Fixes #39590 Closes #53514 r? @pnkfelix
2018-11-05For feature-gate-nll test, turn off testing modes that externally enable NLL.Felix S. Klock II-24/+11
2018-11-03Added tests.Alexander Regueiro-0/+24
2018-11-02Remove deprecated unstable `#[panic_implementation]`Vadim Petrochenkov-32/+0
It was superseded by `#[panic_handler]`
2018-11-02Fix tracking issue numbers for some unstable featuresVadim Petrochenkov-12/+12
2018-10-31Fix feature gate only being checked on first repr attr.Cameron Hart-2/+26
2018-10-27feature-gate lint reasonsZack M. Davis-0/+15
We take stability seriously, so we shy away from making even seemingly "trivial" features insta-stable.
2018-10-27Correct alignment of atomic types and (re)add Atomic{I,U}128Oliver Middleton-7/+43
LLVM requires that atomic loads and stores be aligned to at least the size of the type.