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

Reduce std_unicode’s public API #40189

Merged
merged 2 commits into from
Mar 3, 2017
Merged

Conversation

SimonSapin
Copy link
Contributor

@SimonSapin SimonSapin commented Mar 1, 2017

  • Only keep one copy of the UTF8_CHAR_WIDTH table instead of one of each of libcore and libstd_unicode.

  • Move the utf8_char_width function to core::str under the str_internals unstable feature.

  • Remove std_unicode::str::is_utf16. 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())
    }

@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 @aturon (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.

… instead of one of each of libcore and libstd_unicode.

Move the `utf8_char_width` function to `core::str`
under the `str_internals` unstable feature.
@SimonSapin SimonSapin changed the title Only keep one copy of the UTF8_CHAR_WIDTH table. Reduce std_unicode’s public API Mar 1, 2017
@alexcrichton
Copy link
Member

Travis looks like it may be failing?

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.iter().cloned()).all(|r| r.is_ok())
}
```
@SimonSapin
Copy link
Contributor Author

SimonSapin commented Mar 2, 2017

Ah, yes. It looks like ./x.py test src/libstd does not run tests in src/libcollectionstest, but ./x.py test src/libcollections does.

Should be fixed now.

@alexcrichton
Copy link
Member

@bors: r+

@bors
Copy link
Contributor

bors commented Mar 2, 2017

📌 Commit 24b39c5 has been approved by alexcrichton

@bors
Copy link
Contributor

bors commented Mar 3, 2017

⌛ Testing commit 24b39c5 with merge 1476105...

bors added a commit that referenced this pull request Mar 3, 2017
Reduce std_unicode’s public API

 * Only keep one copy of the `UTF8_CHAR_WIDTH` table instead of one of each of libcore and libstd_unicode.
* Move the `utf8_char_width` function to `core::str` under the `str_internals` unstable feature.
* Remove `std_unicode::str::is_utf16`. 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())
   }
   ```
@bors
Copy link
Contributor

bors commented Mar 3, 2017

☀️ Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 1476105 to master...

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.

5 participants