Skip to main content

wire_name

Function wire_name 

Source
pub fn wire_name(member: &Ident) -> String
Expand description

The client’s name for a slot NO declaration renamed: the household fold — a raw prefix dropped, a trailing underscore eaten, the rest lowerCamel.

So not_in is notIn, starts_with is startsWith, and the two Rust spellings of the keyword slot — r#in and in_ — both land on in. It is the SAME fold every other emitted wire member takes: [crate::emit::wire] owns it, and this is the door a front end asks it through, so that a composed slot and a record’s column cannot come to disagree about what a Rust name looks like on the wire.

Public because the DUPLICATE refusal needs it. Two fields folding onto one wire name is a declaration this door cannot honour — the second registration would replace the first and the parse would read one key twice — and the only place that can be seen is where the tokens are, so the front end folds every member and compares.