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

protected vs private (Simplex_tree) #1146

Open
mglisse opened this issue Oct 18, 2024 · 0 comments
Open

protected vs private (Simplex_tree) #1146

mglisse opened this issue Oct 18, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@mglisse
Copy link
Member

mglisse commented Oct 18, 2024

In the Simplex_tree, many types, functions and members are marked private. I wonder if we should mark some of them protected instead. The effect would be the same for someone using the Simplex_tree directly, but it would give advanced users (and possibly ourselves?) a chance to implement additional functions in a derived class, which may be quite hard using only the public interface.
That doesn't mean that undocumented private details would become stable interfaces though, anyone using them would still have to check with each release if things still work.

@mglisse mglisse added the enhancement New feature or request label Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant