-
Notifications
You must be signed in to change notification settings - Fork 178
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
Compile against Rust Stable #17
Comments
Is this now complete with the changes merged from #38 ? |
@pastoraleman I'm going to leave this open because we introduced some work-arounds in #38 to compile against 1.9.0 stable. When I'll update the issue to reflect that change |
Did you consider using https://crates.io/crates/unicode-segmentation? |
@Yamakaky Correct me if I'm wrong, but it seems to me that the only places where this crate can be used is in Completer and "word" actions where the boundaries are specific (not conforming to unicode standard). And we still need to iterate on chars when reading the standard input stream... |
Oh, ok. |
Looks like this can now be closed! :) |
Negative ! |
Oh, I see now. It compiles against stable, but there's a few workarounds/reimplementations for features that aren't yet stable. |
|
2.0 released |
Currently we take advantage of some non-stabilized rust APIs but eventually we will want to be able to compile against Rust stable. The below links are tracking issues that need to be closed out before we can compile against rust stable.
Update June 6 2016: #38 introduced workaround changes that allowed rustyline to be compiled against rust stable (1.9.0). These changes should eventually replaced by
Read::chars
andencode_utf8
after they become stabilized in the standard library.TO-DO
Read::chars
encode_utf8
str_char
path_relative_from
vec::Drain
The text was updated successfully, but these errors were encountered: