diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-08-15 00:02:24 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-08-15 00:02:24 +0200 |
| commit | 0bed4d1f1c87f88dc60e8751602934ab1ca75e5e (patch) | |
| tree | d8c504243720c4e18cc7bf36b8ac143cb93cb91e /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp | |
| parent | 13a52890dde8cfeb95069d77c223ac37c0cf3a46 (diff) | |
| parent | 5ae03863ded632b6cedeed29cc53e9c69fe5b56b (diff) | |
| download | rust-0bed4d1f1c87f88dc60e8751602934ab1ca75e5e.tar.gz rust-0bed4d1f1c87f88dc60e8751602934ab1ca75e5e.zip | |
Rollup merge of #125970 - RalfJung:before_exec, r=m-ou-se
CommandExt::before_exec: deprecate safety in edition 2024 Similar to `set_var`, we had to find out after 1.0 was released that `before_exec` should have been unsafe. We partially rectified this by deprecating that function a long time ago, but since https://github.com/rust-lang/rust/pull/124636 we have the ability to also deprecate the safety of the old function and make it a *hard error* to call the old function outside `unsafe` in the next edition. So just in case anyone still uses the old function, let's ensure this can't be ignored when moving code to the new edition. Cc `@rust-lang/libs-api` Tracking: - https://github.com/rust-lang/rust/issues/124866
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions