webdav: remove unnecessary "n.byExpiryIndex = -1".
These occur after a heap.Remove call, and heap.Remove calls
byExpiry.Pop, which already sets n.byExpiryIndex to -1.
The memLS.consistent method in lock_test.go checks that the expiry
fields are all consistent.
Change-Id: I09f5d02999e4635f15d1723f89a86b951ed95950
Reviewed-on: https://go-review.googlesource.com/3563
Reviewed-by: Dave Cheney <dave@cheney.net>
Reviewed-by: Nick Cooper <nmvc@google.com>
diff --git a/webdav/lock.go b/webdav/lock.go
index 4bc4465..a5634e7 100644
--- a/webdav/lock.go
+++ b/webdav/lock.go
@@ -193,7 +193,6 @@
}
if n.byExpiryIndex >= 0 {
heap.Remove(&m.byExpiry, n.byExpiryIndex)
- n.byExpiryIndex = -1
}
n.details.Duration = duration
if n.details.Duration >= 0 {
@@ -277,7 +276,6 @@
})
if n.byExpiryIndex >= 0 {
heap.Remove(&m.byExpiry, n.byExpiryIndex)
- n.byExpiryIndex = -1
}
}
