From 74f9f64971cdf5fd52f3619d7bdd38bb8b22626c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=CE=94ndre?= Date: Sat, 27 Aug 2016 15:02:37 +0200 Subject: [PATCH] JSONText & GzippedText are safe in 1.7 1.7 contains this commit https://github.com/golang/go/commit/4e0cd1eeef419b221fda3dd3966be71095f0b4ce which resolves https://github.com/golang/go/issues/13905. --- README.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/README.md b/README.md index 55155d00..e3956e82 100644 --- a/README.md +++ b/README.md @@ -26,9 +26,7 @@ This breaks backwards compatibility, but it's in a way that is trivially fixable (`s/JsonText/JSONText/g`). The `types` package is both experimental and not in active development currently. -More importantly, [golang bug #13905](https://github.com/golang/go/issues/13905) -makes `types.JSONText` and `types.GzippedText` _potentially unsafe_, **especially** -when used with common auto-scan sqlx idioms like `Select` and `Get`. +* Using Go 1.6 and below with `types.JSONText` and `types.GzippedText` can be _potentially unsafe_, **especially** when used with common auto-scan sqlx idioms like `Select` and `Get`. See [golang bug #13905](https://github.com/golang/go/issues/13905). ### Backwards Compatibility