Maxminddb Golang Versions Save

• The methods on the maxminddb.Reader struct now return an error if called on a closed database reader. Previously, this could cause a segmentation violation when using a memory-mapped file.
• The Close method on the maxminddb.Reader struct now sets the underlying buffer to nil, even when using FromBytes or Open on Google App Engine.
• No longer uses constants from syscall

• Fix incorrect index being used when decoding into anonymous struct fields. PR #42 by Andy Bursavich.

• The database decoder now does bound checking when decoding data from the database. This is to help ensure that the reader does not panic when given a corrupt database to decode. Closes #37.
• The reader will now return an error on a data structure with a depth greater than 512. This is done to prevent the possibility of a stack overflow on a cyclic data structure in a corrupt database. This matches the maximum depth allowed by libmaxminddb. All MaxMind databases currently have a depth of less than five.

• Added appengine build tag for Windows. When enabled, memory-mapping will be disabled in the Windows build as it is for the non-Windows build. Pull request #35 by Ingo Oeser.
• SetFinalizer is now used to unmap files if the user fails to close the reader. Using r.Close() is still recommended for most use cases.
• Previously, an unsafe conversion between []byte and string was used to avoid unnecessary allocations when decoding struct keys. The decoder now relies on a compiler optimization on string([]byte) map lookups to achieve this rather than using unsafe.

New release for those using tagged releases.