pkgsrc/devel/go-gls/distinfo

$NetBSD: distinfo,v 1.1 2016/08/21 09:14:25 bsiegert Exp $

SHA1 (gls-4.2.0.tar.gz) = 6fa513402b6571eaa564cee4f27b5261de49cae1
RMD160 (gls-4.2.0.tar.gz) = 5079484ad141a888941ab1648d772f8b94302cd5
SHA512 (gls-4.2.0.tar.gz) = 1bf9e8c7ab69c8754173129f16b1ac81e2635c75cbdfd9be34ca019b47a64ce489f29bdef3c35c2ef2e9ea60ba441b6b5f1417eec393733bc6dc62f9e017adc3
Size (gls-4.2.0.tar.gz) = 6464 bytes
New package, go-gls-4.2.0. Every so often, a thread shows up on the golang-nuts asking for some form of goroutine-local-storage, or some kind of goroutine id, or some kind of context. There are a few valid use cases for goroutine-local-storage, one of the most prominent being log line context. One poster was interested in being able to log an HTTP request context id in every log line in the same goroutine as the incoming HTTP request, without having to change every library and function call he was interested in logging. It is my duty to point you to https://blog.golang.org/context, which is how Google solves all of the problems you'd perhaps consider using this package for at scale. 2016-08-21 11:14:25 +02:00			$NetBSD: distinfo,v 1.1 2016/08/21 09:14:25 bsiegert Exp $

			`SHA1 (gls-4.2.0.tar.gz) = 6fa513402b6571eaa564cee4f27b5261de49cae1`
			`RMD160 (gls-4.2.0.tar.gz) = 5079484ad141a888941ab1648d772f8b94302cd5`
			`SHA512 (gls-4.2.0.tar.gz) = 1bf9e8c7ab69c8754173129f16b1ac81e2635c75cbdfd9be34ca019b47a64ce489f29bdef3c35c2ef2e9ea60ba441b6b5f1417eec393733bc6dc62f9e017adc3`
			`Size (gls-4.2.0.tar.gz) = 6464 bytes`