Skip to content
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

Bump minimum rust version #26

Closed
jrraymond opened this issue Nov 25, 2018 · 5 comments
Closed

Bump minimum rust version #26

jrraymond opened this issue Nov 25, 2018 · 5 comments

Comments

@jrraymond
Copy link
Collaborator

Are there features fixedbitset would benefit from but cannot use without bumping the minimum rust version?

@bluss
Copy link
Member

bluss commented Nov 25, 2018

I've added a bug label breaking-change which is a good way to track such changes, and also to save and catch up on them when it's a good time for breaking changes.

@bluss
Copy link
Member

bluss commented Nov 25, 2018

There are no dependencies or dev-deps even, so we're quite free. Using quickcheck could be good, and then we would be in the "rat race", it requires Rust 1.22. at the moment. I don't have a strong urge for any major jumps.

  • Using RangeBounds trait from std would be neat, but that's all the way up at Rust 1.28.

@bluss
Copy link
Member

bluss commented Aug 21, 2019

@jrraymond I'd propose transferring this crate into the petgraph organization. What do you think? Do you want to join the org, too? (It's entirely optional)

@jrraymond
Copy link
Collaborator Author

@bluss I think that's a good idea. I'd like to join the org too.

@bluss
Copy link
Member

bluss commented Oct 6, 2019

Fixed by #35 - now Rust 1.31.

@bluss bluss closed this as completed Oct 6, 2019
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