You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Small rename refactoring to clarify meaning in the code:
- The concept of "prev step" is only used in SharedDomains as
GetLatest() is used as prev value of next mutation
- Inside GetLatest() chain of calls it is actually just the step whose
that latest mutation occurred, "prev step" sounds strange and confusing
when reading the code
- Most of GetLatest() chain of calls are already using only "step" as
the named variable, so this PR just completes the standardization of
naming.
Copy file name to clipboardExpand all lines: db/state/temporal_mem_batch.go
+21-21Lines changed: 21 additions & 21 deletions
Original file line number
Diff line number
Diff line change
@@ -37,10 +37,10 @@ const (
37
37
put
38
38
)
39
39
40
-
typedataWithPrevStepstruct {
41
-
data[]byte
42
-
prevStep kv.Step
43
-
diriodir
40
+
typedataWithStepstruct {
41
+
data []byte
42
+
step kv.Step
43
+
diriodir
44
44
}
45
45
46
46
// TemporalMemBatch - temporal read-write interface - which storing updates in RAM. Don't forget to call `.Flush()`
@@ -50,8 +50,8 @@ type TemporalMemBatch struct {
50
50
getCacheSizeint
51
51
52
52
latestStateLock sync.RWMutex
53
-
domains [kv.DomainLen]map[string]dataWithPrevStep
54
-
storage*btree2.Map[string, dataWithPrevStep] // TODO: replace hardcoded domain name to per-config configuration of available Guarantees/AccessMethods (range vs get)
53
+
domains [kv.DomainLen]map[string]dataWithStep
54
+
storage*btree2.Map[string, dataWithStep] // TODO: replace hardcoded domain name to per-config configuration of available Guarantees/AccessMethods (range vs get)
0 commit comments