-
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
Move style guide to rust-lang/rust #102239
Conversation
r? @ehuss (rust-highfive has picked a reviewer for you, use r? to override) |
9c7fbd8
to
9a72a66
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to trust that the guide itself is the same as it was in the other repo.
This looks good to me :)
@bors r+ |
I could certainly see moving the style guide under the rust-lang org, but I'm not sure whether moving into the main repo here is the right move. To be clear, I'm not necessarily opposed, just unsure of the best path forward. I recognize that we've yet to finalize our approach to evolving the style guide text, but either way I suspect that we'll end up relying on git tags to capture markers/milestones for the prior version. Is that something we could feasibly do if the guide lives here? I.e. if we end up going the edition-bound route, which tag(s) would we be able to have in this repo that capture the 2015-2021 versions of the style guide? |
And going to remove the approval for the moment to allow for a bit more discussion @bors r- |
👍 for pausing this PR; the only reason I went ahead was because doing so was in the RFC. @calebcartwright wrote:
I can see a couple different options there:
|
You are 100% correct, I just somehow completely overlooked this rather important detail during the RFC, my apologies. I remain unopposed to this change but have a final question or two I should've asked on the original RFC which I'll pose over in rust-lang/rfcs#3320 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bors r+
@bors r+ |
Rollup of 8 pull requests Successful merges: - rust-lang#102110 (Migrate rustc_passes diagnostics) - rust-lang#102187 (Use correct location for type tests in promoted constants) - rust-lang#102239 (Move style guide to rust-lang/rust) - rust-lang#102578 (Panic for invalid arguments of `{integer primitive}::ilog{,2,10}` in all modes) - rust-lang#102811 (Use memset to initialize readbuf) - rust-lang#102890 (Check representability in adt_sized_constraint) - rust-lang#102913 (unify `IsPattern` and `IsImport` enum in `show_candidates`) - rust-lang#102924 (rustdoc: remove unused classes from sidebar links) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Per RFC 3309.