about summary refs log tree commit diff
path: root/src/test/ui/feature-gates
AgeCommit message (Collapse)AuthorLines
2019-10-07[RFC 2091] Add #[track_caller] attribute.Ayose-0/+18
- The attribute is behind a feature gate. - Error if both #[naked] and #[track_caller] are applied to the same function. - Error if #[track_caller] is applied to a non-function item. - Error if ABI is not "rust" - Error if #[track_caller] is applied to a trait function. Error codes and descriptions are pending.
2019-10-06Update ui testsGuillaume Gomez-1/+2
2019-10-03plugin_registrary: use normal deprecation instead of hard coded warning.Mazdak Farrokhzad-11/+23
2019-10-03Deprecate `#![plugin]` and `#[plugin_registrar]`.Mazdak Farrokhzad-2/+19
2019-09-30Stabilize macros in `extern` blocksVadim Petrochenkov-57/+0
Add some tests for macros in extern blocks, remove duplicate tests
2019-09-28Rollup merge of #64763 - GuillaumeGomez:long-err-explanation-E0734, r=estebankMazdak Farrokhzad-2/+3
Add E0734 and its long explanation Part of https://github.com/rust-lang/rust/issues/61137
2019-09-27Update ui testsGuillaume Gomez-2/+3
2019-09-26Adjust & --bless tests due to no longer downgrading NLL errors on 2015.Mazdak Farrokhzad-26/+8
2019-09-22Point at correct span for parenthesized typesEsteban Küber-2/+2
2019-09-15resolve: Tweak "cannot find" wording for attributesVadim Petrochenkov-62/+62
2019-09-14Rollup merge of #64462 - petrochenkov:remattr, r=CentrilMazdak Farrokhzad-8/+8
feature_gate: Remove dead code from attribute checking https://github.com/rust-lang/rust/pull/63468 is merged, so all attributes go through name resolution now, so we can remove code that previously performed some checks for attributes not going through resolution.
2019-09-14feature_gate: Merge various attribute gating functionsVadim Petrochenkov-8/+8
2019-09-14Ban non-extern rust intrinsicsMark Rousskov-81/+125
Intrinsics can only be defined by the compiler.
2019-09-09Rollup merge of #63468 - c410-f3r:attrs, r=petrochenkovMazdak Farrokhzad-136/+84
Resolve attributes in several places Resolve attributes for Arm, Field, FieldPat, GenericParam, Param, StructField and Variant. This PR is based on @petrochenkov work located at https://github.com/petrochenkov/rust/commit/83fdb8d598c1a871d40b21faed64ee698b74f814.
2019-09-09Resolve attributes in several placesCaio-136/+84
Arm, Field, FieldPat, GenericParam, Param, StructField and Variant
2019-09-08Rollup merge of #64263 - crlf0710:improve_wording, r=petrochenkovMazdak Farrokhzad-7/+7
Replace "feature gated" wording with "unstable".
2019-09-08Improve wording.Charles Lew-7/+7
2019-09-08Rollup merge of #64066 - petrochenkov:softstab, r=matthewjasperMazdak Farrokhzad-0/+17
Support "soft" feature-gating using a lint Use it for feature-gating `#[bench]`. Closes https://github.com/rust-lang/rust/issues/63798.
2019-09-07Turn `soft_unstable` into a future-compatibility lintVadim Petrochenkov-0/+3
2019-09-07Support "soft" feature-gating using a lintVadim Petrochenkov-0/+14
Use it for feature-gating `#[bench]`
2019-09-05Remove rustc_diagnostic_macros featureMark Rousskov-33/+0
2019-08-23`--bless` some tests due to message format change.Mazdak Farrokhzad-14/+14
2019-08-20Remove async_await feature gate tests.Mazdak Farrokhzad-103/+0
2019-08-16Feature gate 'yield ?' pre-expansion.Mazdak Farrokhzad-1/+25
2019-08-15resolve: Move macro resolution traces from `Module`s to `Resolver`Vadim Petrochenkov-6/+6
Traces already contain module info without that. It's easy to forget to call `finalize_*` on a module. In particular, macros enum and trait modules weren't finalized. By happy accident macros weren't placed into those modules until now.
2019-08-05Don't recommend `extern crate` syntaxKornel-3/+3
2019-08-02Replace "existential" by "opaque"varkor-4/+4
2019-08-02Switch existential_type to type_alias_impl_traitvarkor-38/+36
2019-07-29Rollup merge of #63092 - Centril:update-impl-trait-gates, r=varkorMazdak Farrokhzad-2/+2
Update `impl Trait` gate issues cc https://github.com/rust-lang/rust/issues/63065 cc https://github.com/rust-lang/rust/issues/63063 r? @varkor cc @alexreg
2019-07-29Rollup merge of #63077 - petrochenkov:nolangfeat, r=petrochenkovMazdak Farrokhzad-13/+6
cleanup: Remove some language features related to built-in macros They are now library features. Cleanup after https://github.com/rust-lang/rust/pull/62086. The unstable book files are moved because tidy complained.
2019-07-29Update existential_type + impl_trait_in_bindings issue numbers.Mazdak Farrokhzad-2/+2
2019-07-28cleanup: Remove some language features related to built-in macrosVadim Petrochenkov-13/+6
They are now library features.
2019-07-28--bless tests due to new subslice syntax.Mazdak Farrokhzad-18/+18
2019-07-28Use new 'p @ ..' syntax in tests.Mazdak Farrokhzad-3/+3
2019-07-27Fix issues with git converting CRLF to CRVadim Petrochenkov-2/+5
UI tests now run on asmjs-unknown-emscripten, ignore tests with inline assembly which is not supported on emscripten targets
2019-07-26Introduce built-in macros through libcoreVadim Petrochenkov-1/+5
2019-07-25Rollup merge of #62736 - lqd:polonius_tests3, r=matthewjasperMazdak Farrokhzad-2/+3
Polonius: fix some cases of `killed` fact generation, and most of the `ui` test suite Since basic Polonius functionality was re-enabled by @matthewjasper in #54468, some tests were still failing in the polonius compare-mode. This PR fixes all but one test in the `ui` suite by: - fixing some bugs in the fact generation code, related to the `killed` relation: Polonius would incorrectly reject some NLL-accepted code, because of these missing `killed` facts. - ignoring some tests in the polonius compare-mode: a lot of those manually test the NLL or migrate mode, and the failures were mostly artifacts of the test revisions, e.g. that `-Z polonius` requires full NLLs. Some others were also both failing with NLL and succeeding with Polonius, which we can't encode in tests at the moment. - blessing the output of some tests: whenever Polonius and NLL have basically the same errors, except for diagnostics differences, the Polonius output is blessed. Whenever we've advanced into a less experimental phase, we'll want to revisit these cases (much like we did on the NLL test suite last year) to specifically work on diagnostics. Fact generation changes: - we now kill loans on the destination place of `Call` terminators - we now kill loans on the locals destroyed by `StorageDead` - we now also handle assignments to projections: killing the loans on a either a deref-ed local, or the ones whose `borrowed_place` conflicts with the current place. One failing test remains: an overflow during fact generation, on a case of polymorphic recursion (and which I'll continue investigating later). This adds some tests for the fact generation changes, with some simple Polonius cases similar to the existing smoke tests, but also for some cases encountered in the wild (in the `rand` crate for example). A more detailed write-up is available [here](https://hackmd.io/CjYB0fs4Q9CweyeTdKWyEg?view) with an explanation for each test failure, the steps taken to resolve it (as a commit in the current PR), NLL and Polonius outputs (and diff), etc. Since they've worked on this before, and we've discussed some of these failures together: r? @matthewjasper
2019-07-23normalize use of backticks for compiler messages in remaining modulesSamy Kacimi-11/+11
https://github.com/rust-lang/rust/issues/60532
2019-07-22Ignore feature-gate-nll.rs in Polonius compare modelqd-2/+3
This is a test about turning the NLL feature gate on, ignored by the NLL compare-mode.
2019-07-21normalize use of backticks in compiler messages for librustc/hirSamy Kacimi-5/+5
https://github.com/rust-lang/rust/issues/60532
2019-07-19Auto merge of #62684 - petrochenkov:scopevisit, r=davidtwcobors-91/+43
resolve: Improve candidate search for unresolved macro suggestions Use same scope visiting machinery for both collecting suggestion candidates and actually resolving the names. The PR is better read in per-commit fashion with whitespace changes ignored (the first commit in particular moves some code around). This should be the last pre-requisite for https://github.com/rust-lang/rust/pull/62086. r? @davidtwco
2019-07-18Auto merge of #61749 - davidtwco:rfc-2203-const-array-repeat-exprs, r=eddybbors-0/+24
rustc/rustc_mir: Implement RFC 2203. This PR implements RFC 2203, allowing constants in array repeat expressions. Part of #49147. r? @eddyb
2019-07-18Rollup merge of #62764 - ↵Mark Rousskov-1/+1
fakenine:normalize_use_of_backticks_compiler_messages_p7, r=alexreg normalize use of backticks in compiler messages for librustc/lint https://github.com/rust-lang/rust/issues/60532
2019-07-18Rollup merge of #62712 - limira:self-type-help, r=estebankMark Rousskov-6/+6
Update the help message on error for self type Fix #62609
2019-07-18resolve: Use `feature(custom_attribute)` fallback only if the feature is enabledVadim Petrochenkov-91/+43
Normally `#![feature(...)]` shouldn't change behavior, but custom attributes in particular are in the process of retirement, and we should not produce a message telling to enable them. It also helps with unifying diagnostics for unresolved macros.
2019-07-17normalize use of backticks in compiler messages for librustc/lintSamy Kacimi-1/+1
https://github.com/rust-lang/rust/issues/60532
2019-07-16Update the help message on error for self typeLimira-6/+6
2019-07-13review commentsEsteban Küber-14/+14
2019-07-13Tweak wording in feature gate errorsEsteban Küber-50/+50
2019-07-11Remove feature gate `dropck_parametricity` completelyLzu Tao-75/+0
Therefore we also remove `#[unsafe_destructor_blind_to_params]` attribute completly.