-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
s/compiler-flags/compile-flags
in compiletest
#94243
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
Hm, I definitely think the validation is a good thing. I'm wondering if we should get stricter about what's present in test headers that looks like it might be a directive (but didn't get parsed as one) -- it's probably pretty rare that unintentionally users write things that look akin to directives? Would you be up for adjusting compiletest to lint against unparsed name/value directives, at least? Those seem like the easiest to catch. Eventually we might want to consider moving them to some kind of Rust-like |
@Mark-Simulacrum, sure, denying |
Yeah, essentially -- my hope is that there's not too many false positives (maybe we can ignore some specific names to avoid common false positives if needed). |
I can try this. @rustbot author |
@compiler-errors |
Ah, yeah, have kinda ignored this. I will work on it this week! |
Hm, probably won't get around to fixing this in the general case. @Mark-Simulacrum, can we merge this as-is? Otherwise I'll just close this. @rustbot ready |
I'm fine with merging as-is. @bors r+ |
📌 Commit 52dd0b6 has been approved by |
⌛ Testing commit 52dd0b6 with merge 24f73cee380c44349067b397bb0b2c74508f71b4... |
…, r=Mark-Simulacrum `s/compiler-flags/compile-flags` in compiletest Also make compiletest panic so this doesn't happen in the future! I literally always forget which it's called, so I wanted to make my life easier in the future. Also open to the possibility of parsing both.
@bors retry (included in rollup) |
☀️ Test successful - checks-actions |
This benchmark run did not return any relevant results. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. |
Also make compiletest panic so this doesn't happen in the future! I literally always forget which it's called, so I wanted to make my life easier in the future.
Also open to the possibility of parsing both.