-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Group all ABI tests. #62593
Group all ABI tests. #62593
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nikomatsakis (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. |
Heh GitHub is showing this as |
@kper I think I wouldn't move all of those tests, specifically not the ones in their own sub-directories (like Other than that, this seems good. |
@eddyb Most of the files I moved are in subdirectories. So should I move them all back or just |
Hmm, I'm less sure now. Let's see what other @rust-lang/compiler people think. |
Always a challenge! I think I would keep things that are grouped under RFCs specifically -- are there any? -- but I think tests in generic sounding directories like Going forward, I want some kind of tagging system where we can include keywords, so that we have a "primary organization" which is oriented around RFCs (or, more generally, stabilization units), I think, but a "secondary organization" for more general categories. Although, writing this out, it makes me wonder if the primary organization should rather be the "language area" or something, with tags being used to record things related to a particular stabilization unit. Well, either way. =) The bottom line is that no one hierarchy is best... |
@rust-lang/compiler @nikomatsakis @kper |
Ping from triage. @eddyb any updates on this? cc @rust-lang/compiler |
@kper We recently moved things out from the |
r? @Centril since he seems more up to date than I am =) |
The grouping led to a lot of `mv`. Therefore, some relative paths were wrong. In this commit the dependent files were also moved so that the paths work again.
@Centril ok, rebased. But the |
@kper Alright, thank you. You'll need to do the same reorganization in the |
@Centril ok, I reorganized it again. This time, I did not touch |
I'm also conflicted like Niko re. @bors r+ |
📌 Commit 4a8ff5b has been approved by |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
@bors r- ^-- |
@Centril because |
I think so yeah. |
@bors r+ |
📌 Commit 26ee99e has been approved by |
Group all ABI tests. r? @eddyb Closes rust-lang#62401
Group all ABI tests. r? @eddyb Closes rust-lang#62401
Rollup of 7 pull requests Successful merges: - #62593 (Group all ABI tests.) - #63173 (Use libunwind from llvm-project submodule for musl targets) - #63535 (Continue refactoring resolve and hygiene) - #63539 (Suggest Rust 2018 on `<expr>.await` with no such field) - #63584 (libcore: more cleanups using `#![feature(associated_type_bounds)]`) - #63612 (Do not suggest `try_into` for base types inside of macro expansions) - #63615 (Fix typo in DoubleEndedIterator::nth_back doc) Failed merges: r? @ghost
The macro tests are not about ABI at all, I'm going to move them back into their old place. |
r? @eddyb
Closes #62401