-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Readiness to be a dependency for rustc? #105
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
Comments
I don't have a problem with that, but I would personally recommend to wait until I release 0.1.0 I want to move to a TOML based configuration file, add multilingual support and move optional features to "plugins" that can be enabled through the configuration file. So it will be a "breaking" release. I assume that being a rustc dependency adds some constraints to breaking changes? |
Not currently. Almost nothing in the ecosystem is 1.0 in general, so all of the dependencies have breaking changes and get updated whenever someone wants to update them, and then they have to fix it as well.
Lots:
Ah, well given |
In that case, I don't have any objection. |
Great! It's not totally clear when the Cargo-based system will actually land, so it might be post-1.0 anyway. Just wanted to hear your thoughts. 👍 |
In rust-lang/rust#31590 (comment), we're discussing how to generate the longform docs in the new Cargo-based build system.
Is mdBook up for this yet? I don't have any particular reason why it would not, but figured I'd ask first. 😄
The text was updated successfully, but these errors were encountered: