diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2025-02-11 02:53:44 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-02-11 02:53:44 +0100 |
| commit | 38f4c1f49a10f1647279e5e8cb6cffb49789ab91 (patch) | |
| tree | 4fdcc2b72e29299735b51003aa346b74c53aceba /compiler/rustc_codegen_gcc | |
| parent | c92aae90e4bcdcc6978e3c3ca9f01777220b356c (diff) | |
| parent | cd9d39e3604680db58acbe409590d495e883d053 (diff) | |
| download | rust-38f4c1f49a10f1647279e5e8cb6cffb49789ab91.tar.gz rust-38f4c1f49a10f1647279e5e8cb6cffb49789ab91.zip | |
Rollup merge of #136603 - workingjubilee:move-abi-versioning-into-ast, r=compiler-errors
compiler: gate `extern "{abi}"` in ast_lowering
I don't believe low-level crates like `rustc_abi` should have to know or care about higher-level concerns like whether the ABI string is stable for users. These implementation details can be made less open to public inspection. This way the code that governs stability is near the code that enforces stability, and compiled together.
It also abstracts away certain error messages instead of constantly repeating them.
A few error messages are simply deleted outright, instead of made uniform, because they are either too dated to be useful or redundant with other diagnostic improvements we could make. These can be pursued in followups: my first concern was making sure there wasn't unnecessary diagnostics-related code in `rustc_abi`, which is not well-positioned to understand what kind of errors are going to be generated based on how it is used.
r? ``@ghost``
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions