Description: Skip IsFloat64AJSONInteger(math.SmallestNonzeroFloat64/2) test
 Go 1.17 increased the precision of math.SmallestNonzeroFloat64, so now
 math.SmallestNonzeroFloat64/2 correctly returns the integer 0, whereas
 Go <= 1.16 returned 5e-324.  See https://github.com/golang/go/issues/44058
Author: Anthony Fok <foka@debian.org>
Origin: vendor
Bug: https://github.com/go-openapi/swag/issues/59
Last-Update: 2021-10-19
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/convert_test.go
+++ b/convert_test.go
@@ -209,7 +209,7 @@
 	assert.True(t, IsFloat64AJSONInteger(minJSONFloat))
 	assert.True(t, IsFloat64AJSONInteger(1/0.01*67.15000001))
 	assert.False(t, IsFloat64AJSONInteger(math.SmallestNonzeroFloat64))
-	assert.False(t, IsFloat64AJSONInteger(math.SmallestNonzeroFloat64/2))
+	// assert.False(t, IsFloat64AJSONInteger(math.SmallestNonzeroFloat64/2))
 	assert.True(t, IsFloat64AJSONInteger(math.SmallestNonzeroFloat64/3))
 	assert.True(t, IsFloat64AJSONInteger(math.SmallestNonzeroFloat64/4))
 }