[GitHub] [kvrocks] PragmaTwice edited a discussion: About code comments in kvrocks

["PragmaTwice (via GitHub)" <gi...@apache.org>]

GitHub user PragmaTwice edited a discussion: About code comments in kvrocks

I have always believed that the code of kvrocks lacks comments, including the following aspects:

Firstly, many classes and functions in kvrocks lack documentation comments, making it difficult for developers to understand the meaning and important information of these classes and functions.

```c++
// what does the class Something do
// some important notice for developers to use Something 
class Something {
  // what does the function Something::f do
  // some important notice for developers to use Something::f
  // explaination of the input parameter a typed A
  // explaination of the return value typed B
  B f(A a);
}
```

Secondly, kvrocks lacks a unified comment identifier. Common identifiers generally include TODO and FIXME. TODO is used to express that there are some matters unresolved or unfinished in the code here, while FIXME is used to express that there are some issues in the code here that need to be fixed.

```c++
// TODO: blablabla
doSomething();

// FIXME: blablabla
doAnotherThing();
```

GitHub link: https://github.com/apache/kvrocks/discussions/1781

----
This is an automatically sent email for issues@kvrocks.apache.org.
To unsubscribe, please send an email to: issues-unsubscribe@kvrocks.apache.org