khepri_tree: Make tree_v*()
and keep_while_conds_revidx_v*()
opaque types
#299
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
They should only be known by
khepri_tree
.How
The definition of
#tree{}
is moved to thekhepri_tree
module and accessor functions are added and exported.The types
tree()
andkeep_while_conds_revidx()
are kept as regular types because the opaque subtypes they group together are used directly. Moreover, if the generic types were marked as opaque too, Dialyzer would enter some infinite loop and never return.At the same time, we rename
khepri_tree.hrl
tokhepri_node.hrl
. It no longer defines#tree{}
and is now dedicated to the definition of#node{}
.