commit | f8e07eb60ff0c8520fc75c4ff5d4979fe5d3998f | [log] [tgz] |
---|---|---|
author | Joel Galenson <jgalenson@google.com> | Tue Aug 24 20:20:55 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Tue Aug 24 20:20:55 2021 +0000 |
tree | d0ee06504f67c40a7c5a06e2c036f8a3a8f4ee2f | |
parent | 6e1516a4c638658e3df17cac86ec191d69702cb8 [diff] | |
parent | 6a82ca0d9b6e5b379571ef781ad9b81245f749d7 [diff] |
Update TEST_MAPPING am: df3d36afcf am: b8de81efe9 am: 3b445e275d am: 4f5918f331 am: 6a82ca0d9b Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/heck/+/1806083 Change-Id: I2d144f51ce89b654d5010c5620d6f7976fbd5b27
This library exists to provide case conversion between common cases like CamelCase and snake_case. It is intended to be unicode aware, internally consistent, and reasonably well performing.
Word boundaries are defined as the “unicode words” defined in the unicode_segmentation
library, as well as within those words in this manner:
That is, “HelloWorld” is segmented Hello|World
whereas “XMLHttpRequest” is segmented XML|Http|Request
.
Characters not within words (such as spaces, punctuations, and underscores) are not included in the output string except as they are a part of the case being converted to. Multiple adjacent word boundaries (such as a series of underscores) are folded into one. (“hello__world” in snake case is therefore “hello_world”, not the exact same string). Leading or trailing word boundary indicators are dropped, except insofar as CamelCase capitalizes the first word.
PRs of additional well-established cases welcome.
This library is a little bit opinionated (dropping punctuation, for example). If that doesn't fit your use case, I hope there is another crate that does. I would prefer not to receive PRs to make this behavior more configurable.
Bug reports & fixes always welcome. :-)
The minimum supported Rust version for this crate is 1.32.0. This may change in minor or patch releases, but we probably won't ever require a very recent version. If you would like to have a stronger guarantee than that, please open an issue.
heck is distributed under the terms of both the MIT license and the Apache License (Version 2.0).
See LICENSE-APACHE and LICENSE-MIT for details.