Behnam Esfahbod

Yeah, agreed generally. Although, it needs some CI configuration to test everything clearly. When `no_std`, we can indeed add `unic::ascii` to fill in the gap where needed.

Re #21, the idea is to change the table-creation and data-table matching codes to perform ASCII lookups via a direct array lookup, and all the rest of Unicode via b-tree...

Many of the packages are now `no_std`. Let's track down the rest for the next release.

Okay, now getting back to this, which is mostly about categorizing Binary properties... Let's start with hi-pri ones, and develop the UCD sub-component based on the application, and we can...

Hey, Zibi! Sorry for the delay here! This is definitely a priority now and would be great to have you help with the API design. One of the things we're...

Thanks for the update, @zbraniecki. Glad to see these crates are published! What I have in mind as the `Locale` model for UNIC is a superset of Unicode/CLDR Locales, so...

Right. Agreed that having the property under `unic::ucd::normal` as a separate crate is the best option. Although it comes with the cost of making it public, which is not encouraged,...

Oops! You're right. `Quick_Check` is indeed recommended to be exposed. So, yeah, we can even expose its types in `unic-ucd`.

Right. And I'm not sure why it's consuming the source. Could be intentional, just to prevent accidental usage after `nfc()` is available. If there's no impl reason to keep it...

Agreed that we probably need two (or more) sets of API for these functionalities. Working on `&str` can be very different, performance-wise and borrow-wise, from char-stream. Right now we have...