You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
In the Simplex_tree, many types, functions and members are marked
private
. I wonder if we should mark some of themprotected
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.
The text was updated successfully, but these errors were encountered: