Anthony Romano e9d096ae6b mvcc: don't allocate end revision while computing range ...

Use 'nil' since it's only reading a single key. Also preallocates
the result slice based on limit / number of revisions fetched.

Fixes #8208

2017-07-06 15:59:27 -07:00

..

backend

…

mvccpb

…

doc.go

…

index_test.go

…

index.go

…

key_index_test.go

…

key_index.go

…

kv_test.go

…

kv_view.go

…

kv.go

…

kvstore_bench_test.go

…

kvstore_compaction_test.go

…

kvstore_compaction.go

…

kvstore_test.go

mvcc: don't allocate end revision while computing range

2017-07-06 15:59:27 -07:00

kvstore_txn.go

mvcc: don't allocate end revision while computing range

2017-07-06 15:59:27 -07:00

kvstore.go

mvcc: don't allocate end revision while computing range

2017-07-06 15:59:27 -07:00

metrics_txn.go

…

metrics.go

…

revision_test.go

…

revision.go

…

util.go

…

watchable_store_bench_test.go

…

watchable_store_test.go

…

watchable_store_txn.go

…

watchable_store.go

…

watcher_bench_test.go

…

watcher_group.go

…

watcher_test.go

…

watcher.go

…