+1 I'm for long and descriptive names over short and counterintuitive. I think, abbreviations shouldn't be mandatory, as they often obscure the meaning of used names.
One-letter abbreviations should be removed from the list at all. When I see a variable *c*, I can't tell, whether it's a char, collection, callable or a closure, even if I remember the rules by heart. Denis вт, 16 окт. 2018 г. в 19:01, Eduard Shangareev <eduard.shangar...@gmail.com >: > Igniters, > > I want to discuss the appendix of our code-style: > https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules. > > First of all, there is no any mention that it is a mandatory part. > > Secondly, some of them are very unintuitive and even misleading. For > example, cp. In current realization, it could mean not only copy but > checkpoint. Other example, proto... Would you get that it is protocol? > > Thirdly, the recommended plugin highlights even parts of multiword names. > It provokes to used creepy names as > locCpPartitionsInProgress, needCpPartitions and so on. > > So, I want to start a discussion for > 1. revising the list of abbreviations, > 2. stop using them for multi-word names, > 3. and make them not mandatory at all (what it is actually already true, > because of no any mention in the main code-style article). >
