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

Remove std_unicode::str::is_utf16 #40190

Closed
wants to merge 1 commit into from

Conversation

SimonSapin
Copy link
Contributor

It was only accessible through the #[unstable] crate std_unicode.

It has never been used in the compiler or standard library since 47e7a05 added it in 2012 “for OS API interop”. It can be replaced with a one-liner:

fn is_utf16(slice: &[u16]) -> bool {
    std::char::decode_utf16(s).all(|r| r.is_ok())
}

It was only accessible through the `#[unstable]` crate std_unicode.

It has never been used in the compiler or standard library
since 47e7a05 added it in 2012
“for OS API interop”.
It can be replaced with a one-liner:

```rust
fn is_utf16(slice: &[u16]) -> bool {
    std::char::decode_utf16(s).all(|r| r.is_ok())
}
```
@rust-highfive
Copy link
Collaborator

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @brson (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

@SimonSapin
Copy link
Contributor Author

This conflicts with #40189, should I put both commits in one PR?

@SimonSapin
Copy link
Contributor Author

Moved on top of #40189.

@SimonSapin SimonSapin closed this Mar 1, 2017
@SimonSapin SimonSapin deleted the utf16-nope branch March 1, 2017 22:26
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