[IMPORTANT] CODE STYLE STANDARD

[imkiva]

Seeing #11, I found that we can no longer rely on external tools or IDE to help us ensure the unification of code style, so I think we should specify a code standard, according to which the code style will be checked in the future code review.
见及请之十一，夫复恃外具以护代码体之一，可乎？故私以为，宜以一准，后之码者，具以此格校之是也。

LET'S SOLVE PROBLEMS ONE BY ONE.
请一一而治之。

The first problem to be solved is braces, here is my opinion:
所急者，大括号也，吾言如是：

namespace NS {
    class FUCK {
    public:
        FUCK() {
            // do something
        }
    };
}

[mikecovlee]

I agree. But I think the braces of function should be placed at the next line.
Why not using astyle as formatting tools? CLion can't run in command line environment. Actually I don't use IDEs very often.

[mikecovlee]

My suggest is that using astyle -A4 -N as our official formatting options.

[mikecovlee]

Otherwise, pls speak modern Chinese instead of classical Chinese.

[imkiva]

My suggest is that using astyle -A4 -N as our official formatting options.

astyle is not so wise as you can see my review comments in #11, which clion does better.

And, I don't like to open a terminal and type commands every time I want to format my code, especially commands with extra arguments.

If you prefer a command line formatter, clang-format is a good choice, and can be configured with file .clang-format, which clion also supports.

[imkiva]

braces of function should be placed at the next line.

Why should we put the braces in different positions and increase coding complexity? It's easy to think that our braces are not standardized at all.

[mikecovlee]

Some additional proposal:

1. A virtual destructor is required in non-final classes/structures to avoid unnecessary memory leak.
2. Declaring all constructors explicitly or using default and delete if you don't want.

[imkiva]

Added 1 rule:

• Do not eliminate param name in function declaration, which is bad for readability.