about summary refs log tree commit diff
path: root/tests/ui/array-slice-vec
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2025-01-15 12:06:56 +0000
committerbors <bors@rust-lang.org>2025-01-15 12:06:56 +0000
commit341f60327fa5302732a4be366949c16f91870b6a (patch)
tree319c3df4a34ed17a8b34f3a69331aa8c63444045 /tests/ui/array-slice-vec
parent2776bdfe423c9fdfcd6313d678f0852ea26f1309 (diff)
parent767d4fe64e3644ffcd89b3265fdee6659d08786a (diff)
downloadrust-341f60327fa5302732a4be366949c16f91870b6a.tar.gz
rust-341f60327fa5302732a4be366949c16f91870b6a.zip
Auto merge of #134353 - oli-obk:safe-target-feature-unsafe-by-default, r=wesleywiser
Treat safe target_feature functions as unsafe by default [less invasive variant]

This unblocks
* #134090

As I stated in https://github.com/rust-lang/rust/pull/134090#issuecomment-2541332415 I think the previous impl was too easy to get wrong, as by default it treated safe target feature functions as safe and had to add additional checks for when they weren't. Now the logic is inverted. By default they are unsafe and you have to explicitly handle safe target feature functions.

This is the less (imo) invasive variant of #134317, as it doesn't require changing the Safety enum, so it only affects FnDefs and nothing else, as it should.
Diffstat (limited to 'tests/ui/array-slice-vec')
0 files changed, 0 insertions, 0 deletions