Skip to content

doc: document absence of stability guarantees #10828

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
Nov 22, 2021
Merged

Conversation

matklad
Copy link
Member

@matklad matklad commented Nov 22, 2021

bors r+
🤖


* `rust-project.json` is a de-facto stable format for non-cargo build systems.
It is probably ok enough, but was definitely stabilized implicitly.
Lesson for the future: when designing API which could become a stability boundary, don't wait for the first users until you stabilize it.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's fine to wait for the first users to get feedback, even if it results in breaking changes later.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that's the opt-in bit later. I'd be happier if rust-project had a requirement of specifying "I_hereby_opt_into_instabbility": true field, such that the moment we remove the field becomes stabilization.

@bors
Copy link
Contributor

bors bot commented Nov 22, 2021

@bors bors bot merged commit 806d7d7 into rust-lang:master Nov 22, 2021
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants