about summary refs log tree commit diff
path: root/src/test/ui/reachable
AgeCommit message (Collapse)AuthorLines
2021-01-16Move some tests to more reasonable directories - 2Caio-0/+25
Address comments Update limits
2020-04-11rustc: Add a warning count upon completionRoccoDev-0/+2
2020-03-22Normalize wording of privacy access labelsEsteban Küber-1/+1
2020-02-06rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros.Eduard-Mihai Burtescu-8/+8
2020-02-06rustc: rename -Zexternal-macro-backtrace to -Zmacro-backtrace.Eduard-Mihai Burtescu-8/+8
2020-01-24Normalise notes with the/isvarkor-27/+27
2020-01-16resolve: Point at the private item definitions in privacy errorsVadim Petrochenkov-1/+7
2019-12-14Revert "Remove `#![feature(never_type)]` from tests."Niko Matsakis-22/+29
This reverts commit 8f6197f39f7d468dfc5b2bd41dae4769992a2f83.
2019-11-21Gate fallback via `#![feature(never_type_fallback)]`.Mazdak Farrokhzad-3/+4
2019-11-21Remove `#![feature(never_type)]` from tests.Mazdak Farrokhzad-32/+24
Also remove `never_type` the feature-gate test.
2019-10-15Organize `never_type` testsMazdak Farrokhzad-0/+295
Also move {run-fail -> ui}/never_type
2019-09-21Do not trigger unreachable lint in async body and Use span labelsEsteban Küber-226/+122
2019-09-18Some formatting cleanupAaron Hill-1/+1
2019-09-18Make note better when all arms in a `match` divergeAaron Hill-6/+6
2019-09-18Point at original span when emitting unreachable lintAaron Hill-0/+217
Fixes #64590 When we emit an 'unreachable' lint, we now add a note pointing at the expression that actually causes the code to be unreachable (e.g. `return`, `break`, `panic`). This is especially useful when macros are involved, since a diverging expression might be hidden inside of a macro invocation.
2019-09-07Reduce span to function name in unreachable callsShiqing-5/+5
2019-07-06Enforce 'cond: bool' in while-expr + improve reachability diags.Mazdak Farrokhzad-23/+19
2019-07-03Migrate compile-pass annotations to build-passYuki Okushi-2/+2
2019-05-10Various test changesMazdak Farrokhzad-6/+16
2019-03-11Update testsVadim Petrochenkov-24/+24
2018-12-25Remove licensesMark Rousskov-259/+54
2018-10-16Remove outdated testvarkor-19/+6
2018-07-23Match errors using the callsite of macro expansionsFederico Poli-5/+16
2018-05-16Remove empty filesJane Lusby-0/+0
2018-05-11unary op filter, dereference hintRoman Stoliar-3/+1
2018-05-11added missing implementation hintRoman Stoliar-0/+2
2018-04-20Revert stabilization of `feature(never_type)`.Felix S. Klock II-7/+7
This commit is just covering the feature gate itself and the tests that made direct use of `!` and thus need to opt back into the feature. A follow on commit brings back the other change that motivates the revert: Namely, going back to the old rules for falling back to `()`.
2018-04-13Rename must-compile-successfully into compile-passGuillaume Gomez-2/+2
2018-03-14Fix ui test errorsAndrew Cann-1/+1
2018-03-14Make coerce_never lint an errorAndrew Cann-28/+11
Remove the coerce_never lint and make the behaviour an error.
2018-03-14stabilise feature(never_type)Andrew Cann-54/+37
Replace feature(never_type) with feature(exhaustive_patterns). feature(exhaustive_patterns) only covers the pattern-exhaustives checks that used to be covered by feature(never_type)
2018-03-14update testsGuillaume Gomez-1/+1
2018-02-26Update UI testsVadim Petrochenkov-57/+57
2018-02-25Update ui testsGuillaume Gomez-0/+1
2017-12-10Add must-compile-successfully comment to appropriate ui tests.Tommy Ip-0/+4
2017-11-30make coercions to `!` in unreachable code a hard errorAriel Ben-Yehuda-6/+23
This was added to cover up a lazy extra semicolon in #35849, but does not actually make sense. This is removed as a part of the stabilization of `never_type`.
2017-11-26mention nightly in -Z external-macro-backtrace noteAlex Burka-11/+11
2017-11-24Merge cfail and ui tests into ui testsOliver Schneider-49/+50
2017-11-20address review commentsAlex Burka-11/+11
2017-11-19use -Z flag instead of env varAlex Burka-11/+11
2017-11-19update UI testsAlex Burka-11/+11
2017-08-09rustc: Rearchitect lints to be emitted more eagerlyAlex Crichton-1/+13
In preparation for incremental compilation this commit refactors the lint handling infrastructure in the compiler to be more "eager" and overall more incremental-friendly. Many passes of the compiler can emit lints at various points but before this commit all lints were buffered in a table to be emitted at the very end of compilation. This commit changes these lints to be emitted immediately during compilation using pre-calculated lint level-related data structures. Linting today is split into two phases, one set of "early" lints run on the `syntax::ast` and a "late" set of lints run on the HIR. This commit moves the "early" lints to running as late as possible in compilation, just before HIR lowering. This notably means that we're catching resolve-related lints just before HIR lowering. The early linting remains a pass very similar to how it was before, maintaining context of the current lint level as it walks the tree. Post-HIR, however, linting is structured as a method on the `TyCtxt` which transitively executes a query to calculate lint levels. Each request to lint on a `TyCtxt` will query the entire crate's 'lint level data structure' and then go from there about whether the lint should be emitted or not. The query depends on the entire HIR crate but should be very quick to calculate (just a quick walk of the HIR) and the red-green system should notice that the lint level data structure rarely changes, and should hopefully preserve incrementality. Overall this resulted in a pretty big change to the test suite now that lints are emitted much earlier in compilation (on-demand vs only at the end). This in turn necessitated the addition of many `#![allow(warnings)]` directives throughout the compile-fail test suite and a number of updates to the UI test suite.
2017-07-02Revert "Change error count messages"Ariel Ben-Yehuda-19/+19
This reverts commit 5558c64f33446225739c1153b43d2e309bb4f50e.
2017-05-27Add invalid unary operator usage error codeGuillaume Gomez-1/+1
2017-05-24Change error count messagesMichael Kohl-19/+19
See #33525 for details.
2017-03-30cherry-pick over the tests I wrote for the reachability codeNiko Matsakis-0/+1023
For the most part, the current code performs similarly, although it differs in some particulars. I'll be nice to have these tests for judging future changes, as well.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-04-24 13:20:40 +0000