about summary refs log tree commit diff
path: root/src/test/ui/binding
AgeCommit message (Collapse)AuthorLines
2023-01-11Move /src/test to /testsAlbert Larsan-2717/+0
2022-11-23Suggest `.clone()` or `ref binding` on E0382Esteban Küber-0/+16
2022-10-01bless ui testsMaybe Waffle-5/+5
2022-09-23Restore ignore tagFlorian Bartels-1/+0
This test case actually requires std::process.
2022-08-03Warn about dead tuple struct fieldsFabian Wolff-3/+3
2022-07-13remove untagged_union feature gateRalf Jung-2/+2
2022-04-14make unaligned_reference warning visible in future compat reportRalf Jung-0/+52
2022-04-14make unaligned_references lint deny-by-defaultRalf Jung-10/+10
2021-12-11Rollup merge of #91718 - RalfJung:unaligned_references, r=nagisaMatthias Krüger-0/+4
give more help in the unaligned_references lint Cc https://github.com/rust-lang/rust/issues/82523#issuecomment-988138440 ``@kaisq``
2021-12-09Add needs-unwind to tests that depend on panickingDavid Koloski-0/+1
This directive isn't automatically set by compiletest or x.py, but can be turned on manually for targets that require it.
2021-12-09give more help in the unaligned_references lintRalf Jung-0/+4
2021-10-25Edit error messages for rustc_resolve::AmbiguityKind variantspierwill-2/+4
Emit description of the ambiguity as a note. Co-authored-by: Noah Lev <camelidcamel@gmail.com> Co-authored-by: Vadim Petrochenkov <vadim.petrochenkov@gmail.com>
2021-09-26Remove box syntax from most places in src/test outside of the issues direst31-24/+13
2021-08-30`feature(const_generics)` -> `feature(const_param_types)`lcnr-13/+1
2021-03-27make unaligned_refereces future-incompat lint warn-by-default, and remove ↵Ralf Jung-38/+38
the safe_packed_borrows lint that it replaces
2021-03-20Move some tests to more reasonable directories - 5Caio-0/+24
2021-02-17replace if-let and while-let with `if let` and `while let`Takayuki Maeda-2/+2
2020-12-26update testsBastian Kauschke-21/+21
2020-10-17Suggest minimal subset features in `incomplete_features` lintYuki Okushi-0/+1
2020-08-08Be consistent when describing a move as a 'partial' in diagnosticsAaron Hill-12/+12
When an error occurs due to a partial move, we would use the world "partial" in some parts of the error message, but not in others. This commit ensures that we use the word 'partial' in either all or none of the diagnostic messages. Additionally, we no longer describe a move out of a `Box` via `*` as a 'partial move'. This was a pre-existing issue, but became more noticable when the word 'partial' is used in more places.
2020-07-26Remove more obsolete test flagsOliver Scherer-1/+0
2020-05-09adjust testsRalf Jung-1/+2
2020-05-03resolve: Relax fresh binding disambiguation slightly to fix regressionVadim Petrochenkov-0/+1
2020-04-11rustc: Add a warning count upon completionRoccoDev-2/+2
2020-04-10--bless youMazdak Farrokhzad-8/+8
2020-04-10copy test cases to `if let` as well.Felix S. Klock II-2/+59
2020-04-10Update src/test/ui/binding/issue-53114-safety-checks.rsFelix S Klock II-1/+1
Co-Authored-By: Mazdak Farrokhzad <twingoow@gmail.com>
2020-04-10Update src/test/ui/binding/issue-53114-borrow-checks.rsFelix S Klock II-1/+1
Co-Authored-By: Mazdak Farrokhzad <twingoow@gmail.com>
2020-04-10tests encoding current behavior for various cases of "binding" to _.Felix S. Klock II-0/+243
The `_` binding form is special, in that it encodes a "no-op": nothing is actually bound, and thus nothing is moved or borrowed in this scenario. Usually we do the "right" thing in all such cases. The exceptions are explicitly pointed out in this test case, so that we keep track of whether they are eventually fixed.
2020-03-15resolve: Prevent fresh bindings from shadowing ambiguity itemsVadim Petrochenkov-0/+88
Correctly treat const generic parameters in fresh binding disambiguation
2020-01-18slice_patterns: remove gates in testsMazdak Farrokhzad-6/+3
2019-12-14Revert "Remove `#![feature(never_type)]` from tests."Niko Matsakis-1/+1
This reverts commit 8f6197f39f7d468dfc5b2bd41dae4769992a2f83.
2019-11-21Gate fallback via `#![feature(never_type_fallback)]`.Mazdak Farrokhzad-0/+1
2019-11-21Remove `#![feature(never_type)]` from tests.Mazdak Farrokhzad-1/+0
Also remove `never_type` the feature-gate test.
2019-10-29Rollup merge of #65832 - tlively:emscripten-exception-handling, r=alexcrichtonTyler Mandry-1/+1
Re-enable Emscripten's exception handling support Passes LLVM codegen and Emscripten link-time flags for exception handling if and only if the panic strategy is `unwind`. Sets the default panic strategy for Emscripten targets to `unwind`. Re-enables tests that depend on unwinding support for Emscripten, including `should_panic` tests. r? @alexcrichton
2019-10-27Gather together usefulness testsNadrieril-14/+0
I took most tests that were testing only for match exhaustiveness, pattern refutability or match arm reachability, and put them in the same test folder.
2019-10-25Re-enable Emscripten's exception handling supportThomas Lively-1/+1
Passes LLVM codegen and Emscripten link-time flags for exception handling if and only if the panic strategy is `unwind`. Sets the default panic strategy for Emscripten targets to `unwind`. Re-enables tests that depend on unwinding support for Emscripten, including `should_panic` tests.
2019-10-16Upgrade Emscripten targets to use upstream LLVM backendThomas Lively-1/+2
- Compatible with Emscripten 1.38.46-upstream or later upstream. - Refactors the Emscripten target spec to share code with other wasm targets. - Replaces the old incorrect wasm32 C call ABI with the correct one, preserving the old one as wasm32_bindgen_compat for wasm-bindgen compatibility. - Updates the varargs ABI used by Emscripten and deletes the old one. - Removes the obsolete wasm32-experimental-emscripten target. - Uses EMCC_CFLAGS on CI to avoid the timeout problems with #63649.
2019-10-05Revert "Auto merge of #63649 - tlively:emscripten-upstream-upgrade, ↵Tyler Mandry-2/+1
r=alexcrichton" This reverts commit 7870050796e5904a0fc85ecbe6fa6dde1cfe0c91, reversing changes made to 2e7244807a7878f6eca3eb7d97ae9b413aa49014.
2019-10-04Upgrade Emscripten targets to use upstream LLVM backendThomas Lively-1/+2
- Refactors the Emscripten target spec to share code with other wasm targets. - Replaces the incorrect wasm32 C call ABI with the old asmjs version, which is correct for both wasm32 and JS. - Updates the varargs ABI used by Emscripten and deletes the old one. - Removes the obsolete wasm32-experimental-emscripten target. - Temporarily makes Emscripten targets use panic=abort by default because supporting unwinding will require an LLVM patch.
2019-07-28Use new 'p @ ..' syntax in tests.Mazdak Farrokhzad-2/+2
2019-07-27tests: Move run-pass tests without naming conflicts to uiVadim Petrochenkov-0/+2268
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-01-15 01:26:35 +0000