const char *keyName(const Key *key)

(bullet points are in order of appearance)

[x] Abbreviations used in function names must be defined in the Glossary
[x] Function names should neither be too long, nor too short
[ ] Function name should be clear and unambiguous
- [ ] Function name might lead to confusions with keyGetName(), make their intentions more clear in their names
[x] Abbreviations used in parameter names must be defined in the Glossary
[x] Parameter names should neither be too long, nor too short
[x] Parameter names should be clear and unambiguous

(only in PRs)

Symbol versioning is correct for breaking changes
ABI/API changes are forward-compatible (breaking backwards-compatibility to add additional symbols is fine)

Function parameters should use enum types instead of boolean types wherever sensible
[x] Wherever possible, function parameters should be const
[x] Wherever possible, return types should be const
[x] Functions should have the least amount of parameters feasible

[x] Functions should do exactly one thing
[x] Function name has the appropriate prefix
[x] Order of signatures in kdb.h.in is the same as Doxygen
[x] No functions with similar purpose exist
- [ ] keyUnescapedName might be considered too similar

[x] Function code is fully covered by tests
[ ] All possible error states are covered by tests
- [ ] empty keyName is not covered in tests
All possible enum values are covered by tests
[x] No inconsistencies between tests and documentation