This fix vastly deteriorates the performance of BufferBackend::resolve which is why I added StringInterner::resolve_unchecked for users to mitigate the performance issue on their side if they are sure to always use valid symbols.
Even with the regressed performance for resolve the BufferBackend is the choice for especially memory constrained environments.
Closes https://github.com/Robbepop/string-interner/issues/49.
This fix vastly deteriorates the performance of
BufferBackend::resolve
which is why I addedStringInterner::resolve_unchecked
for users to mitigate the performance issue on their side if they are sure to always use valid symbols. Even with the regressed performance forresolve
theBufferBackend
is the choice for especially memory constrained environments.Benchmarks: