diff options
| author | 许杰友 Jieyou Xu (Joe) <39484203+jieyouxu@users.noreply.github.com> | 2024-07-08 13:04:30 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-07-08 13:04:30 +0800 |
| commit | 29c1a43403350615606290b8e05a6a5f4183733d (patch) | |
| tree | e791e1cdf1ab68321880a2254f0f6e6d559555c3 /tests/codegen/patchable-function-entry/patchable-function-entry-both-flags.rs | |
| parent | 2c16d65c1e1fc007900debc4993bba3098bc077c (diff) | |
| parent | 18c248b6564ea750321cf9765f700def4265e490 (diff) | |
| download | rust-29c1a43403350615606290b8e05a6a5f4183733d.tar.gz rust-29c1a43403350615606290b8e05a6a5f4183733d.zip | |
Rollup merge of #126881 - WaffleLapkin:unsafe-code-affected-by-fallback-hard-in-2024, r=compiler-errors
Make `NEVER_TYPE_FALLBACK_FLOWING_INTO_UNSAFE` a deny-by-default lint in edition 2024 I don't actually really care about this, but ``@traviscross`` asked me to do this, because lang team briefly discussed this before. (TC here:) Specifically, our original FCPed plan included this step: - Add a lint against fallback affecting a generic that is passed to an `unsafe` function. - Perhaps make this lint `deny-by-default` or a hard error in Rust 2024. That is, we had left as an open question strengthening this in Rust 2024, and had marked it as an open question on the tracking issue. We're nominating here to address the open question. (Closing the remaining open question helps us to fully mark this off for Rust 2024.) r? ``@compiler-errors`` Tracking: - https://github.com/rust-lang/rust/issues/123748
Diffstat (limited to 'tests/codegen/patchable-function-entry/patchable-function-entry-both-flags.rs')
0 files changed, 0 insertions, 0 deletions