Tracking issue for new command parsing framework

[PragmaTwice]

Search before asking

• I had searched in the issues and found no similar issues.

Motivation

In kvrocks, command parsing is currently done by some primitive array operations, which works fine for simple commands, but when command parsing rules become complex, the code becomes extremely difficult to understand and maintain. In addition, the parsing of data values such as numerics and enumerations is not well encapsulated.

This work was originally described in #598 to provide an easy-to-use parsing framework for parsing redis commands, especially complex redis commands. In addition, another goal of this work is to eliminate redundant string copies, which are currently widespread in kvrocks, and we will try to introduce something like std::string_view or design APIs that make better use of move semantics of std::string.

Solution

working PRs:

• Add StatusOr for error handling in modern C++ style #768
• Add newly designed ParseInt #787
• Add command parser #1032
• Add integer parsing with unit support #1218
• Add ParseFloat and replace stod with it #1227

Are you willing to submit a PR?

• I'm willing to submit a PR!

[git-hulk]

Many thanks for @PragmaTwice bringing those awesome features to the community.