Skip to content

Decide what to do about unstable warnings #11

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

Closed
hannobraun opened this issue Jan 10, 2015 · 1 comment
Closed

Decide what to do about unstable warnings #11

hannobraun opened this issue Jan 10, 2015 · 1 comment

Comments

@hannobraun
Copy link
Owner

Currently, there are a lot of warnings about the use of unstable functionality in the code. If my understanding is correct, nothing unstable will be shipped with stable Rust versions following the release of Rust 1.0. I think it's very desirable for this library to work with stable versions, too.

The best decision for now is probably to wait. A lot of the unstable stuff might still become stable before 1.0. However, if there are still warnings shortly before the 1.0 release, we should probably attempt to replace the code in question with something else, if possible.

@dead10ck
Copy link
Contributor

Yes, I agree, it's a better idea to leave them on for now. As I mentioned in a commit comment, most of them will probably go away as they get marked stable by the Rust team. And some of them are useful, e.g. I saw the warnings about the new slicing syntax. Like you said, if it gets close to 1.0 and there are still unstable warnings, they can be replaced with stable code.

hannobraun added a commit that referenced this issue Jan 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants