-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Improve function naming consistency. #50
Comments
To minimize the number of API changes, it might be useful to consider simplification of a common use case of formatting into an str(Format("{}", 42)); Ideally it should require a single function call. Possible ways to do this:
|
Fixed in version 0.9.0. |
vitaut
added a commit
that referenced
this issue
Jul 26, 2014
vitaut
added a commit
that referenced
this issue
Jul 26, 2014
vitaut
added a commit
that referenced
this issue
Jul 27, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently there is an inconsistency in function naming. Some functions are named according to Google C++ Style Guide:
Format
Print
Clear
ReportSystemError
...
Other follow standard library conventions:
c_str
str
clear
resize
reserve
printf
sprintf
...
The names should be unified before the version 1.0 of the API is released. This is pretty arbitrary, but it's probably better to follow standard library conventions for public API for consistency with
printf
and because its done already for most functions.The text was updated successfully, but these errors were encountered: