-
Notifications
You must be signed in to change notification settings - Fork 2
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
Use single preceding underscores instead of double underscores for private methods and functions #36
Comments
Here are the functions and methods left to change:
|
riley-harper
added a commit
that referenced
this issue
Dec 2, 2022
riley-harper
added a commit
that referenced
this issue
Dec 2, 2022
…s in Training's create comparison features link step
riley-harper
changed the title
Use single preceding underscores instead of double underscores for private methods
Use single preceding underscores instead of double underscores for private methods and functions
Dec 2, 2022
riley-harper
added a commit
that referenced
this issue
Dec 2, 2022
- Rename __apply_regex_substitution() -> _apply_regex_substitution() - Rename __apply_substitution() -> _apply_substitution() - Rename __load_substitutions() -> _load_substitutions()
riley-harper
added a commit
that referenced
this issue
Dec 2, 2022
- Rename __key_count_1() -> _key_count_1() - Rename __key_count_2() -> _key_count_2()
Let's ignore |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a style choice that we've slowly been moving to as we make other changes. Instead of something like
__method()
, we use_method()
.__method()
does some mangling of the name of the method, but_method()
is mostly just a documentation indication that the method is considered private and not part of the public API.Similarly, let's move from
__function()
to_function()
for consistency.The text was updated successfully, but these errors were encountered: