File: control

package info (click to toggle)
golang-github-dghubble-trie 0.1.0-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 116 kB
  • sloc: makefile: 13
file content (35 lines) | stat: -rw-r--r-- 1,307 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
Source: golang-github-dghubble-trie
Section: golang
Priority: optional
Maintainer: Daniel Baumann <daniel@debian.org>
Build-Depends:
 debhelper-compat (= 13),
 dh-sequence-golang,
 dpkg-build-api (= 1),
 golang-any,
Standards-Version: 4.7.0
Homepage: https://github.com/dghubble/trie
Vcs-Browser: https://forgejo.debian.net/golang/golang-github-dghubble-trie
Vcs-Git: https://forgejo.debian.net/golang/golang-github-dghubble-trie
Testsuite: autopkgtest-pkg-go
XS-Go-Import-Path: github.com/dghubble/trie

Package: golang-github-dghubble-trie-dev
Section: golang
Architecture: all
Multi-Arch: foreign
Depends:
 ${misc:Depends},
Description: Fast, zero heap allocation Go Trie for runes or paths (library)
 Package trie implements rune-wise and path-wise Tries
 (https://en.wikipedia.org/wiki/Trie) optimized for Get performance and
 to allocate 0 bytes of heap memory (i.e. garbage) per Get.
 .
 A typical use case is to perform any Put or Delete operations upfront to
 populate the trie, then perform Get operations very quickly. The Tries
 do not synchronize access (not thread-safe).
 .
 When Tries are chosen over maps, it is typically for their space
 efficiency. However, in situations where direct key lookup is not
 possible (e.g. routers), tries can provide faster lookups and avoid key
 iteration.