style: reordered second consequence
CI / Check PR Title (pull_request) Successful in 44s
CI / Go Lint (pull_request) Successful in 1m28s
CI / Markdown Lint (pull_request) Successful in 48s
CI / Makefile Lint (pull_request) Successful in 1m11s
CI / Unit Tests (pull_request) Successful in 1m17s
CI / Fuzz Tests (pull_request) Successful in 1m47s
CI / Mutation Tests (pull_request) Successful in 1m29s

This commit is contained in:
2026-07-04 19:48:23 -04:00
parent 3bc9d63b93
commit 9b5545bf52
+1 -1
View File
@@ -33,8 +33,8 @@ Do not equate them.
- [ ] Update the `README.md` and `doc.go` to reflect these principles. - [ ] Update the `README.md` and `doc.go` to reflect these principles.
- [ ] Update the contributing guide and pull request template to require these principles are met. - [ ] Update the contributing guide and pull request template to require these principles are met.
2. The repository should contain a living document, describing the interface differences between `go-cuckoo` and `map`. 2. The repository should contain a living document, describing the interface differences between `go-cuckoo` and `map`.
(I already started work on branch `docs/interface-congruency-analysis`.)
I should prioritize limiting any incongruencies. I should prioritize limiting any incongruencies.
(I already started work on branch `docs/interface-congruency-analysis`.)
- [ ] Produce the first draft to uncover any current incongruencies. - [ ] Produce the first draft to uncover any current incongruencies.
- [ ] Link the document to the `README.md`. - [ ] Link the document to the `README.md`.
3. Analyze the familiarity of `go-cuckoo`'s current interface. 3. Analyze the familiarity of `go-cuckoo`'s current interface.