Currently, the red-black tree implementation is split between rbTree.hpp and rbTree.inline.hpp. The separation as it is now makes rbTree.hpp less readable and unnecessarily exposes headers for other files including the tree. In particular, it depends on the "os" class, which in turn pulls in many additional headers.
To address these issues, all implementation code should be moved to rbTree.inline.hpp instead. This will improve readability by keeping rbTree.hpp focused on declarations, and will also limit the number of included headers to only what is necessary, also reducing potential header leakage.
To address these issues, all implementation code should be moved to rbTree.inline.hpp instead. This will improve readability by keeping rbTree.hpp focused on declarations, and will also limit the number of included headers to only what is necessary, also reducing potential header leakage.
- links to
-
Review(pr/29082)
openjdk/jdk/29295