Suggestion: adopt a documentation format for docstring

As the number of algorithms are increasing, it might make sense to adopt a single documentation format for docstrings. Following are existing currently:

• Google Docstring: https://google.github.io/styleguide/pyguide.html#s3.8-comments-and-docstrings
• Numpydoc: https://numpydoc.readthedocs.io/en/latest/format.html
• Sphinx: https://sphinx-rtd-tutorial.readthedocs.io/en/latest/docstrings.html

There are editor extensions which help in generating the docstring based on the chosen format like:

• VSCode: https://github.com/NilsJPWerner/autoDocstring
• Neovim: https://github.com/danymat/neogen

The doctest will come under the examples section for each of the above format.

首先比較 issue 中連結的 Google Docstring、Numpydoc 和 Sphinx 格式，包括每種格式如何處理 doctest 範例。查看討論，以確定專案是否已選擇一種格式。當已有共識的文件格式，以及將其套用到演算法 docstring 的明確定義方式時，即視為完成。