about summary refs log tree commit diff
path: root/tests/ui/unsafe
AgeCommit message (Collapse)AuthorLines
2025-08-27Add test batch 1Oneirical-0/+22
2025-08-19bless tests with new lint messagesKarol Zwolak-2/+2
2025-07-25commentsKivooeo-0/+27
2025-07-25move 28 testsKivooeo-0/+27
2025-07-16future-incompat lints: don't link to the nightly edition-guide versiondianne-17/+17
2025-07-10cleaned up some testsKivooeo-2/+5
2025-07-01moved testsKivooeo-0/+18
2025-06-10Loop check anon consts on their ownOli Scherer-6/+6
2025-05-23Emit dummy open drop for unsafe binderMichael Goulet-0/+29
2025-04-30compiletest: Make diagnostic kind mandatory on line annotationsVadim Petrochenkov-4/+6
2025-04-08UI tests: add missing diagnostic kinds where possibleVadim Petrochenkov-1/+1
2025-03-21remove `feature(inline_const_pat)`lcnr-23/+0
2024-12-15Use links to edition guide for edition migrationsEric Huss-33/+33
2024-11-26tests: remove `//@ pretty-expanded` usages许杰友 Jieyou Xu (Joe)-3/+0
Done with ```bash sd '//@ pretty-expanded.*\n' '' tests/ui/**/*.rs ``` and ``` sd '//@pretty-expanded.*\n' '' tests/ui/**/*.rs ```
2024-11-22Stabilize the 2024 editionEric Huss-6/+4
2024-11-16Reword suggestion messageEsteban Küber-1/+1
2024-10-06A raw ref of a deref is always safeMichael Goulet-0/+14
2024-09-18Check params for unsafety in THIRMichael Goulet-0/+38
2024-09-15also stabilize const_refs_to_cellRalf Jung-25/+4
2024-09-15stabilize const_mut_refsRalf Jung-36/+5
2024-08-06Don't Suggest Labeling `const` and `unsafe` BlocksVeera-10/+29
2024-08-06Add TestsVeera-0/+57
2024-07-04Tweak raw-pointer field access and array indexing suggestionsEsteban Küber-4/+6
2024-05-29Use parenthetical notation for `Fn` traitsEsteban Küber-1/+1
Always use the `Fn(T) -> R` format when printing closure traits instead of `Fn<(T,), Output = R>`. Fix #67100: ``` error[E0277]: expected a `Fn()` closure, found `F` --> file.rs:6:13 | 6 | call_fn(f) | ------- ^ expected an `Fn()` closure, found `F` | | | required by a bound introduced by this call | = note: wrap the `F` in a closure with no arguments: `|| { /* code */ }` note: required by a bound in `call_fn` --> file.rs:1:15 | 1 | fn call_fn<F: Fn() -> ()>(f: &F) { | ^^^^^^^^^^ required by this bound in `call_fn` help: consider further restricting this bound | 5 | fn call_any<F: std::any::Any + Fn()>(f: &F) { | ++++++ ```
2024-05-22Cleanup: Fix up some diagnosticsLeón Orell Valerian Liehr-17/+21
2024-05-17Rename Unsafe to SafetySantiago Pastorino-3/+3
2024-02-16[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives许杰友 Jieyou Xu (Joe)-29/+29
2024-02-01`#![feature(inline_const_pat)]` is no longer incompleteMatthew Jasper-1/+0
2024-01-22Auto merge of #120242 - matthiaskrgr:rollup-a93yj3i, r=matthiaskrgrbors-0/+1
Rollup of 10 pull requests Successful merges: - #117910 (Refactor uses of `objc_msgSend` to no longer have clashing definitions) - #118639 (Undeprecate lint `unstable_features` and make use of it in the compiler) - #119801 (Fix deallocation with wrong allocator in (A)Rc::from_box_in) - #120058 (bootstrap: improvements for compiler builds) - #120059 (Make generic const type mismatches not hide trait impls from the trait solver) - #120097 (Report unreachable subpatterns consistently) - #120137 (Validate AggregateKind types in MIR) - #120164 (`maybe_lint_impl_trait`: separate `is_downgradable` from `is_object_safe`) - #120181 (Allow any `const` expression blocks in `thread_local!`) - #120218 (rustfmt: Check that a token can begin a nonterminal kind before parsing it as a macro arg) r? `@ghost` `@rustbot` modify labels: rollup
2024-01-18Consistently warn unreachable subpatternsNadrieril-0/+1
2024-01-15make unsafe_op_in_unsafe_fn MachineApplicable and add it to 2024 compatibilityasquared31415-50/+153
2024-01-13Bless testsGeorge-lewis-0/+5
Update tests
2024-01-05Handle context for const patterns correctlyMatthew Jasper-0/+24
2024-01-05Stabilize THIR unsafeckMatthew Jasper-92/+98
2024-01-05Remove revisions for THIR unsafeckMatthew Jasper-1093/+115
This is to make the diff when stabilizing it easier to review.
2023-12-07recurse into refs when comparing tys for diagnosticsjyn-4/+4
2023-11-24Show number in error message even for one errorNilstrieb-35/+35
Co-authored-by: Adrian <adrian.iosdev@gmail.com>
2023-11-16recover primary span labelEsteban Küber-1/+2
2023-11-06Visit patterns in THIR let expressionsMatthew Jasper-2/+19
This fixes some THIR unsafety checking errors not being emitted for let expressions in these situations.
2023-11-06Add suggestion to THIR unsafe_op_in_unsafe_fn lintMatthew Jasper-30/+246
2023-11-02Pretty print Fn traits in rustc_on_unimplementedMichael Goulet-1/+1
2023-10-25Make THIR unused_unsafe lint consistent with MIRMatthew Jasper-7/+5
Updates THIR behavior to match the changes from #93678
2023-09-14Auto merge of #112038 - Nemo157:edition-2024-unsafe_op_in_unsafe_fn, r=RalfJungbors-0/+33
Change `unsafe_op_in_unsafe_fn` to be `warn`-by-default from edition 2024 This was previously FCPed: https://github.com/rust-lang/rust/issues/71668#issuecomment-1189396886 There were two blocking requirements: * Fix the `unused_unsafe` lint, done in https://github.com/rust-lang/rust/pull/100081 * Have `cargo fix` able to fix the lint, done in https://github.com/rust-lang/rust/pull/112017
2023-09-06add a regression testmojave2-0/+37
2023-09-06Change unsafe_op_in_unsafe_fn to be warn-by-default from edition 2024Wim Looman-0/+33
2023-08-30Test and note unsafe ctor to fn ptr coercionMichael Goulet-0/+25
Also remove a note that I don't consider to be very useful in context.
2023-08-30rustc_layout_scalar_valid_range makes ctors unsafeMichael Goulet-0/+27
2023-07-15Implement "items do not inherit unsafety" for THIR unsafecksyvb-2/+28
2023-06-13Add test cases for suggestions with unsafe operations contained inside macrosWim Looman-11/+100
2023-06-13Add note about unsafe functions body not being unsafeWim Looman-8/+63
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-22 23:25:13 +0000