fix: exemplify differences between map and go-cuckoo table
CI / Check PR Title (pull_request) Successful in 44s
CI / Makefile Lint (pull_request) Successful in 1m18s
CI / Go Lint (pull_request) Successful in 1m30s
CI / Markdown Lint (pull_request) Successful in 48s
CI / Unit Tests (pull_request) Successful in 1m19s
CI / Fuzz Tests (pull_request) Successful in 1m50s
CI / Mutation Tests (pull_request) Successful in 1m32s
CI / Check PR Title (pull_request) Successful in 44s
CI / Makefile Lint (pull_request) Successful in 1m18s
CI / Go Lint (pull_request) Successful in 1m30s
CI / Markdown Lint (pull_request) Successful in 48s
CI / Unit Tests (pull_request) Successful in 1m19s
CI / Fuzz Tests (pull_request) Successful in 1m50s
CI / Mutation Tests (pull_request) Successful in 1m32s
This commit is contained in:
@@ -25,7 +25,7 @@ To resolve this, I'm enforcing two new principles onto the contract of `go-cucko
|
||||
|
||||
These principles should _guide_ the public interface of `go-cuckoo`.
|
||||
Neither should be treated absolutely, though.
|
||||
The behavior of `go-cuckoo` is distinct from `map`.
|
||||
The behavior of `go-cuckoo` is distinct from `map` (e.g. `Put` can fail; see `ErrBadHash`).
|
||||
Do not equate them.
|
||||
|
||||
## Consequences
|
||||
|
||||
Reference in New Issue
Block a user