359002bbeb
Thought of doing this by having a struct and an enum with Default and Alt cases, but not sure if we wanted to have the text in code instead of having “demangling()” and “demangling-alt()” in the ftl file. Don’t like the current way of having structs representing the same-ish and using long names to distinguish their expectations, instead of putting this in an enum and handling the different cases inside the type. I am fine with whichever option the team prefers; also understand having them as separate structs keeps it simple.
6 lines
232 B
Plaintext
6 lines
232 B
Plaintext
symbol_mangling_invalid_symbol_name = symbol-name({$mangled_formatted})
|
|
|
|
symbol_mangling_invalid_trait_item = demangling({$demangling_formatted})
|
|
|
|
symbol_mangling_alt_invalid_trait_item = demangling-alt({$alt_demangling_formatted})
|