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

Replace use of unstable features #38

Merged
merged 4 commits into from
Jun 3, 2016
Merged

Conversation

birkenfeld
Copy link
Contributor

Tested to work with stable rustc 1.9.0.

@kkawakam
Copy link
Owner

kkawakam commented Jun 1, 2016

@birkenfeld can you update the .travis.yml to use stable rust (or maybe pinned to a specific version)?

@kkawakam
Copy link
Owner

kkawakam commented Jun 1, 2016

@gwenn are you doing any changes on your fork right now where going to stable will cause you some issues?

@birkenfeld
Copy link
Contributor Author

@kkawakam sure!

@gwenn
Copy link
Collaborator

gwenn commented Jun 1, 2016

@kkawakam no, I will keep on using the unstable version.

@kkawakam kkawakam merged commit 65f45a3 into kkawakam:master Jun 3, 2016
@kkawakam
Copy link
Owner

kkawakam commented Jun 3, 2016

@birkenfeld I'll push a new version to crates.io soon.

@pwrdwnsys pwrdwnsys mentioned this pull request Jun 3, 2016
5 tasks
brookst added a commit to brookst/skim that referenced this pull request Jan 19, 2017
Use private char iterator as done in kkawakam/rustyline#38 while waiting
for stabilisation of the chars method per rust-lang/rust#27802
This removes the need for `#[feature(io)]` letting skim compile on rust
stable.
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.

3 participants