Source: golang-github-timandy-routine
Section: golang
Maintainer: Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
Uploaders:
 Simon Josefsson <simon@josefsson.org>,
Build-Depends:
 debhelper-compat (= 13),
 dh-sequence-golang,
 dpkg-build-api (= 1),
 golang-any,
 golang-github-stretchr-testify-dev,
Testsuite: autopkgtest-pkg-go
Standards-Version: 4.7.4
Vcs-Browser: https://salsa.debian.org/go-team/packages/golang-github-timandy-routine
Vcs-Git: https://salsa.debian.org/go-team/packages/golang-github-timandy-routine.git
Homepage: https://github.com/timandy/routine
XS-Go-Import-Path: github.com/timandy/routine

Package: golang-github-timandy-routine-dev
Architecture: all
Multi-Arch: foreign
Depends:
 golang-github-stretchr-testify-dev,
 ${misc:Depends},
Description: ThreadLocal for Golang (Go library)
 routine encapsulates and provides some easy-to-use, non-competitive,
 high-performance goroutine context access interfaces, which can help you
 access coroutine context information more gracefully.
 .
 From the very beginning of its design, the Golang language has spared no
 effort to shield the concept of coroutine context from developers,
 including the acquisition of coroutine goid, the state of coroutine
 within the process, and the storage of coroutine context.
 .
 If you have used other languages such as C++, Java and so on, then you
 must be familiar with ThreadLocal, but after starting to use Golang, you
 will be deeply confused and distressed by the lack of convenient
 functions like ThreadLocal.
 .
 Of course, you can choose to use Context, which carries all the context
 information, appears in the first input parameter of all functions, and
 then shuttles around your system.
 .
 And the core goal of routine is to open up another way: Introduce
 goroutine local storage to the Golang world.
 .
 This package contains the Go library.
