Rename RecordOffset to Offset

Author: oschwald

reader_test.go

@@ -311,7 +311,7 @@ func TestDecoder(t *testing.T) {
 		require.NoError(t, result.Err())
 		require.True(t, result.Found())
 
-		res := reader.LookupOffset(result.RecordOffset())
+		res := reader.LookupOffset(result.Offset())
 		require.NoError(t, res.Decode(&testV))
 		verify(testV)
 	}
@@ -564,7 +564,7 @@ func TestNestedOffsetDecode(t *testing.T) {
 			TimeZoneOffset uintptr `maxminddb:"time_zone"`
 		} `maxminddb:"location"`
 	}
-	res := db.LookupOffset(result.RecordOffset())
+	res := db.LookupOffset(result.Offset())
 	require.NoError(t, res.Decode(&root))
 	assert.InEpsilon(t, 51.5142, root.Location.Latitude, 1e-10)
 

result.go

@@ -107,14 +107,14 @@ func (r Result) Found() bool {
 	return r.err == nil && r.offset != notFound
 }
 
-// RecordOffset returns the offset of the record in the database. This can be
-// passed to ReaderDecode. It can also be used as a unique identifier for the
-// data record in the particular database to cache the data record across
-// lookups. Note that while the offset uniquely identifies the data record,
-// other data in Result  may differ between lookups. The offset is only valid
-// for the current database version. If you update the database file, you must
-// invalidate any cache associated with the previous version.
-func (r Result) RecordOffset() uintptr {
+// Offset returns the offset of the record in the database. This can be
+// passed to (*Reader).LookupOffset. It can also be used as a unique
+// identifier for the data record in the particular database to cache the data
+// record across lookups. Note that while the offset uniquely identifies the
+// data record, other data in Result  may differ between lookups. The offset
+// is only valid for the current database version. If you update the database
+// file, you must invalidate any cache associated with the previous version.
+func (r Result) Offset() uintptr {
 	return uintptr(r.offset)
 }