Discarding avoidable dupes of access specifiers

[Anirban166]

Is the use of a duplicate access specifier (e.g.) reasonable? (this seems to be some rationale, but otherwise it seems unnecessary)

[LeStarch]

At very least, we allow those. Most often we break our components (and C++) into sections.

// header comment
public:
    //compiler section
//header comment
public:
    //helper functions
...

Although that particular example file is missing header comments, the sections are still there. It is much easier to read and maintain with those extra access specifiers, so you don't have to look outside the section to find what your current specifier is.