aboutsummaryrefslogtreecommitdiffstats
path: root/proposals
diff options
context:
space:
mode:
authorBryan Newbold <bnewbold@robocracy.org>2018-05-06 19:51:14 -0700
committerBryan Newbold <bnewbold@robocracy.org>2018-05-06 19:51:14 -0700
commit21f48cf852cbdcae38163dd58fb68eaaf9dd70e1 (patch)
tree24472c0af5a48bdd7e8a1db9e4f8007700759443 /proposals
parent89e0315d74741696c497d09ef09320bbffc5bfa1 (diff)
downloaddat-deps-21f48cf852cbdcae38163dd58fb68eaaf9dd70e1.tar.gz
dat-deps-21f48cf852cbdcae38163dd58fb68eaaf9dd70e1.zip
log(M) reviewed by mafintosh
Diffstat (limited to 'proposals')
-rw-r--r--proposals/0000-hyperdb.md3
1 files changed, 0 insertions, 3 deletions
diff --git a/proposals/0000-hyperdb.md b/proposals/0000-hyperdb.md
index c05bd0b..8990bd4 100644
--- a/proposals/0000-hyperdb.md
+++ b/proposals/0000-hyperdb.md
@@ -734,9 +734,6 @@ room" for those changes, or should we call out the potential for future change?
Probably not, should only describe existing solutions. This can be resolved
after Draft.
-Review (or prove?) the `O(log(M))` intuition for `get()` operations. This could
-happen after Draft status.
-
There are implied "reasonable" limits on the size (in bytes) of both keys and
values, but they are not formally specified. Protobuf messages have a hard
specified limit of 2 GByte (due to 32-bit signed arithmetic), and most