Skip to content
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

LLVMWrapper: attractive nuisance macros #83442

Merged
merged 1 commit into from
Mar 25, 2021

Conversation

durin42
Copy link
Contributor

@durin42 durin42 commented Mar 24, 2021

This came up in the review of #83425: it's hard to imagine a use of
LLVM_VERSION_LE() or LLVM_VERSION_EQ() that's not asking for trouble
when a point release gets created, so let's just discard them to prevent
the issue.

@rust-highfive
Copy link
Collaborator

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Mark-Simulacrum (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

@rust-highfive rust-highfive added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Mar 24, 2021
@durin42
Copy link
Contributor Author

durin42 commented Mar 24, 2021

r? @cuviper

@cuviper
Copy link
Member

cuviper commented Mar 24, 2021

Just for clarity, can you fix the commit message to say LE is a problem, rather than LT?

@durin42
Copy link
Contributor Author

durin42 commented Mar 24, 2021

Whoops, fixed that typo (in the PR description: I assume you don't want a force-push to fix the underlying git commit).

@cuviper
Copy link
Member

cuviper commented Mar 24, 2021

I assume you don't want a force-push to fix the underlying git commit

I do want that so we have a clear history.

I understand that force-pushing sometimes obscures reviews, but I think we're fine in this case.

THis came up in the review of rust-lang#83425: it's hard to imagine a use of
LLVM_VERSION_LE() or LLVM_VERSION_EQ() that's not asking for trouble
when a point release gets created, so let's just discard them to prevent
the issue.
@durin42
Copy link
Contributor Author

durin42 commented Mar 24, 2021

force-pushed the commit message typo fix

@cuviper
Copy link
Member

cuviper commented Mar 24, 2021

Thanks!

@bors r+ rollup

@bors
Copy link
Contributor

bors commented Mar 24, 2021

📌 Commit 04961d2 has been approved by cuviper

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Mar 24, 2021
bors added a commit to rust-lang-ci/rust that referenced this pull request Mar 25, 2021
Rollup of 8 pull requests

Successful merges:

 - rust-lang#83041 (stabilize debug_non_exhaustive)
 - rust-lang#83349 (Remove Option::{unwrap_none, expect_none}.)
 - rust-lang#83420 (Add documentation for rustdoc-gui tests)
 - rust-lang#83421 (Add Result::into_err where the Ok variant is the never type)
 - rust-lang#83427 (small cleanups in rustc_errors / emitter)
 - rust-lang#83434 (Update RELEASES.md)
 - rust-lang#83440 (Use intra-doc link in core::cell)
 - rust-lang#83442 (LLVMWrapper: attractive nuisance macros)

Failed merges:

 - rust-lang#83438 (Update RELEASES.md)

r? `@ghost`
`@rustbot` modify labels: rollup
@bors bors merged commit 67436c1 into rust-lang:master Mar 25, 2021
@rustbot rustbot added this to the 1.53.0 milestone Mar 25, 2021
@durin42 durin42 deleted the remove-questionable-macros branch August 24, 2021 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants