The RadixTree is the only managed / safe prefix lookup implementation being developed for distribution from the project at this time. Its name could be simplified to PrefixLookup to help consumers of the Nuget package understand that it is the implementation that is expected to be used in as a default choice (i.e. when they don't already know they want the unsafe trie). While there is already a PrefixLookup wrapper class that wraps the RadixTree, using it as a wrapper reduces performance while being less flexible than using the RadixTree directly.
This will likely require renaming the UnsafeTrie as well, to get away from 'implementation detail' specifc name. At this time I'm unsure if the UnsafeTrie will be modified to all be an unsafe Radix Tree (an experiment worth investigating). If so, the name change for that type should be held off on.
The RadixTree is the only managed / safe prefix lookup implementation being developed for distribution from the project at this time. Its name could be simplified to PrefixLookup to help consumers of the Nuget package understand that it is the implementation that is expected to be used in as a default choice (i.e. when they don't already know they want the unsafe trie). While there is already a PrefixLookup wrapper class that wraps the RadixTree, using it as a wrapper reduces performance while being less flexible than using the RadixTree directly.
This will likely require renaming the UnsafeTrie as well, to get away from 'implementation detail' specifc name. At this time I'm unsure if the UnsafeTrie will be modified to all be an unsafe Radix Tree (an experiment worth investigating). If so, the name change for that type should be held off on.