Skip to content

Conversation

@finnbear
Copy link

@finnbear finnbear commented Sep 18, 2022

@thomcc
Copy link
Member

thomcc commented Sep 18, 2022

The right process for this was likely an ACP rather than an RFC, see https://std-dev-guide.rust-lang.org/feature-lifecycle/api-change-proposals.html for more info. While going through an RFC is possible, it's probably overkill for something like this. You probably should file one here: https://github.com/rust-lang/libs-team/issues/new?assignees=&labels=api-change-proposal%2C+T-libs-api&template=api-change-proposal.md&title=%28My+API+Change+Proposal%29 (unless going through the full RFC process sounds better to you...)

@thomcc thomcc added the T-libs-api Relevant to the library API team, which will review and decide on the RFC. label Sep 18, 2022
@finnbear
Copy link
Author

finnbear commented Sep 18, 2022

The right process for this was likely an ACP rather than an RFC

Oh, alright, thanks for letting me know. I'll go submit an ACP :)

Edit: here it is: rust-lang/libs-team#109

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

T-libs-api Relevant to the library API team, which will review and decide on the RFC.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants