Skip to content

Enable std by default in rand_core; adjust CI targets #409

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

Merged
merged 1 commit into from
Apr 20, 2018

Conversation

dhardy
Copy link
Member

@dhardy dhardy commented Apr 19, 2018

Avoid using --all and --features together (fix #406)

Can we release rand_core 0.1.1 with this change?

Avoid using --all and --features together
@vks
Copy link
Collaborator

vks commented Apr 19, 2018

I think yes, it should not break code, right?

@pitdicker
Copy link
Contributor

Is there a rush to make a release with this? I have not read the thread well, does it stop building on nightly cargo?

@dhardy
Copy link
Member Author

dhardy commented Apr 20, 2018

No, there's not a rush. The only thing that will break is our CI scripts. But enabling std by default seems worthwhile.

@pitdicker
Copy link
Contributor

But enabling std by default seems worthwhile.

Release together with rand 0.5?

And do you think it makes sense to already upgrade to serde 1.0.38? serde-rs/serde#1207 (comment)

@pitdicker pitdicker merged commit bd34459 into rust-random:master Apr 20, 2018
@dhardy
Copy link
Member Author

dhardy commented Apr 20, 2018

1.0.38 is a patch-release so users will be upgraded automatically — therefore no reason we shouldn't use it, I think.

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

Successfully merging this pull request may close these issues.

Update CI not to conflate --all and --features
3 participants