Skip to content
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

Mark more things private #36

Open
shape-warrior-t opened this issue Dec 17, 2023 · 0 comments
Open

Mark more things private #36

shape-warrior-t opened this issue Dec 17, 2023 · 0 comments
Labels
code quality Places where the codebase can be improved.

Comments

@shape-warrior-t
Copy link
Contributor

Some modules, classes, and functions are not currently marked private, even when they are best thought of as implementation details of a specific subteam, module, or class. In particular, there are currently no modules in the codebase that are marked private. It might be a good idea to examine exactly what truly needs to be exposed to other subteams/modules/classes, and change public/private statuses of things accordingly.

@shape-warrior-t shape-warrior-t added the code quality Places where the codebase can be improved. label Dec 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code quality Places where the codebase can be improved.
Projects
None yet
Development

No branches or pull requests

1 participant