-
Notifications
You must be signed in to change notification settings - Fork 52
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
Crate does not compile on stable Rust < 1.36 #31
Comments
Can confirm that I had the same error in the CI for one of my libraries,in a job that uses Rust 1.34 . It would benefit this library to have a minimum required version in the README,and enforce it in CI if it doesn't bump it in minor versions. |
Yes, I've ran into this issue too, building on my pinned version of Rust, which used to build fine on Rust 1.32: |
The PR that introduced this regression seems to be #30. It'd be nice if this could be fixed, and a specific rust version be pinned in the |
After some time trying different versions, it seems like Rust |
Due to a Rust [version regression in `typed-arena`](thomcc/rust-typed-arena#31) we can now only support Rust 1.36. This adds a temporary minimum version of Rust 1.36, and allows failures for Rust 1.32 until this is resolved.
Due to a Rust [version regression in `typed-arena`](thomcc/rust-typed-arena#31) we can now only support Rust 1.36. This adds a temporary minimum version of Rust 1.36, and allows failures for Rust 1.32 until this is resolved.
This crate hasn't made any promises about maintaining compatibility with specific rust versions, just that it will always compile on the stable channel. I think it is reasonable to add a stronger stability guarantee, but doing so requires the CI changes mentioned above and backporting the code to work with older rust versions. If someone is willing to do those things, I would be happy to review the PR and be willing to start making those stronger versioning guarantees from then on out. |
I don't think it's necessary to make a promise on this, but I have found that just having a specific version in the .travis.yml makes me consider whether or not I want to break backwards compatibility on a library, especially if there is an easier work around. It's also nice documentation. :) I might see if I can look at this today. |
Posted a patch at #33! Hope this helps! |
Thank you, we'll check this patch! |
Published 1.6.1 |
Thanks! Really appreciate your work on maintaining this! 👏 |
Hello,
It seems that your librairie does not compile anymore since the 1.6.0, and also, all dependencies does not compile anymore too! (like test-junit)
We are using the nightly-2019-03-06 rust version.
Do you confirm this error ?
Could you check your publication please ?
:/
The text was updated successfully, but these errors were encountered: