Change Details

Currently our clang format file seems to enforce type *name while most of our code base is type* name this generates a lot of code noise in diffs if using features in VS2019 to auto format directly. Further I think the style in the code base type* name makes more sense nowadays looking because I would put the priority on method signatures and not on c-ish data definitions. Want to discuss and clarify it.

Currently our clang format file seems to enforce type *name while most of our code base is type* name this generates a lot of code noise in diffs if using features in VS2019 to auto format directly. Further I think the style in the code base type* name makes more sense nowadays, because I would put the priority on method signatures and not on c-ish data definitions. Want to discuss and clarify it.

Currently our clang format file seems to enforce type *name while most of our code base is type* name this generates a lot of code noise in diffs if using features in VS2019 to auto format directly. Further I think the style in the code base type* name makes more sense nowadays looking, because I would put the priority on method signatures and not on c-ish data definitions. Want to discuss and clarify it.