-
Notifications
You must be signed in to change notification settings - Fork 7
Fixes pack #146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixes pack #146
Conversation
brain5lug
commented
Sep 30, 2025
- make logger a bit faster
- std::forward related fixes
- use std::string_view for call function
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the patch and for your interest in our project! I have no objections except for one nitpick.
@CuriousGeorgiy I've checked linter complaints - they don't relate to the actual code changes, so I suggest to ignore it. The only actual complaints are about writing all the move constructors from the second commit in one line - that's what my nitpick suggests. |
0401fe1
to
320af2d
Compare
Eliminate copying from std::stringstream if complied with C++20 or higher
std::forward were replace std::move for fixed type context where it does not make sense. Some redundant comment were removed as they declare obvious actions under them.
For most of cases encoding fuction such as `call`, `execute` and `prepare` use predefined fixed literal. Those values are best to be expressed as std::string_view literals. std::string_view are really usefull and can be easily createad from any sequense memory areas. There are no changes are required from cliend side as std::string_view can be implicilty coverted from std::string.
320af2d
to
4fecfc2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@brain5lug
Thanks for the patches and your fixes, all neat and shiny! Happy to see you around and chat about tntcxx
code and design if you have any more ideas for improvement.