From be4314389113cc4ebd59fb385dfd396f70d1ea81 Mon Sep 17 00:00:00 2001 From: Andrew Noyes Date: Thu, 7 Mar 2024 12:33:34 -0800 Subject: [PATCH] Tidying --- ConflictSet.cpp | 1 - paper/paper.tex | 2 +- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/ConflictSet.cpp b/ConflictSet.cpp index c08096e..eff4935 100644 --- a/ConflictSet.cpp +++ b/ConflictSet.cpp @@ -534,7 +534,6 @@ Node *getChildNodeGeq(Node *self, int child) { int c = self256->bitSet.firstSetGeq(child); return c >= 0 ? self256->children[c].child : nullptr; } - return nullptr; } void setChildrenParents(Node4 *n) { diff --git a/paper/paper.tex b/paper/paper.tex index f5e43ec..4a7fe1a 100644 --- a/paper/paper.tex +++ b/paper/paper.tex @@ -72,7 +72,7 @@ Each node shows its partial prefix annotated with $(max,point,range)$. \subsection{Checking point reads} -The algorithm for checking point reads follows directly from the definitions of the \emph{point} and \emph{range}. +The algorithm for checking point reads follows directly from the definitions of the \emph{point} and \emph{range} fields. Our input is a key $k$ and a read version $r$, and we must report whether or not the write version $v_{k}$ of $k$ is less than or equal to $r$. In order to find $v_{k}$, we search for the node whose prefix matches $k$. If such a node exists and has \emph{point} set, then $v_{k}$ is its \emph{point} field.