Install-Package rm.Trie -Version 1.3.5
dotnet add package rm.Trie --version 1.3.5
<PackageReference Include="rm.Trie" Version="1.3.5" />
paket add rm.Trie --version 1.3.5
#r "nuget: rm.Trie, 1.3.5"
// Install rm.Trie as a Cake Addin #addin nuget:?package=rm.Trie&version=1.3.5 // Install rm.Trie as a Cake Tool #tool nuget:?package=rm.Trie&version=1.3.5
A trie (prefix tree) data structure implementation in C#.
|.NET||net5.0 net5.0-windows net6.0 net6.0-android net6.0-ios net6.0-maccatalyst net6.0-macos net6.0-tvos net6.0-windows|
|.NET Core||netcoreapp2.0 netcoreapp2.1 netcoreapp2.2 netcoreapp3.0 netcoreapp3.1|
|.NET Standard||netstandard2.0 netstandard2.1|
|.NET Framework||net461 net462 net463 net47 net471 net472 net48|
- No dependencies.
- No dependencies.
NuGet packages (3)
Showing the top 3 NuGet packages that depend on rm.Trie:
This is a .NET standard library that tries to parse and analyze the user agent string and extract as many relevant attributes as possible. The library aims to provides a reliable and extensible user agent parsing, browser and device detection. This is a semantic analyzer, so it doesn't rely on any database (except for some very little lookup tables), that means it is able to parse and recognize every day new kind of user agents and new patterns without updates. That makes the library very fast, flexible and easy to mantain, on the contrary the library can't extract info that are not present on user agent string without a proper mapping. The library doesn't aim to recognize every device in the world (there are several thousands), but it is able to work, analyze and extract all attributes available in the user agent. For most common devices we provide a lookup table in yaml file to identify device brand/model based on the few info available in the user agent. The library can be easily extended thanks to yaml files and a simple syntax (we don't rely on regular expression). Thanks to custom yaml definitions, you can make the library able to identify your company applications/ tools and extract your custom fields.
A spatial index backed by geohashing and Trie (prefix tree) maps. Geometries are encoded as geohashes and stored in a prefix tree, and reverse lookups are performing by encoding the queried geometry and using the prefix tree as an inverted lookup index. The index size can be tuned with the precision parameter. The geohasher and prefix tree map providers can be injected by implementing the IGeohasher and/or IGeohashTrieMap interfaces.
TAO3 is a .NET Interactive extension for writing data transformation quickly.
This package is not used by any popular GitHub repositories.