Skip to main content

store_accepts_non_ascii_identifiers

Function store_accepts_non_ascii_identifiers 

pub async fn store_accepts_non_ascii_identifiers<F: Fixture>(
    open: impl AsyncFn() -> F,
) -> RuleOutcome
Expand description

Non-ASCII identifiers survive, and are not folded into each other.

VT-14. EventType::new and Tag::new reject char::is_control, which is Unicode general category Cc and not ASCII — four doc comments in happenstance-core say ASCII and are wrong about their own code. Category Cf is deliberately not rejected, because U+200C and U+200D are load bearing in Persian, in Devanagari and in every emoji ZWJ sequence, so all three appear here.

The store’s half is a separate obligation from the constructors’: a value the constructor accepts still has to survive a column. What this rejects is an ASCII-only one — VARCHAR under a latin1 collation, SQL Server’s non-N VARCHAR, or a CHECK written against [[:ascii:]] — where the driver transcodes and every codepoint outside the target charset becomes ?. Latin1IdentifierStore is the compiled version.

The two Devanagari types differing only by a vowel sign are the folding half: a collation that normalises or case-folds makes them one type, and the query that should select one selects both.