CLAUDE.md: record that Cargo.lock is gitignored on purpose - #15
Merged
Merged
Conversation
My own board carried this as an inconsistency to settle -- "serialize.rs and reliable.rs commit one; netcode.rs does not" -- framed as if this repo were the outlier. It has it backwards. This .gitignore is hand-written and lists Cargo.lock beside the fuzz artifacts; the other two never mention it, so their locks are committed by OMISSION rather than by decision, and both are near-empty (1 and 2 packages) because those crates have essentially no dependencies. This is the only Rust port with real ones. I had already run cargo generate-lockfile here before checking, which is exactly the failure the hot blocks exist to stop, committed minutes after I finished writing them. The .gitignore is what caught me. Recording it where the next person will hit it first. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
My own board carried this as an inconsistency to settle — "serialize.rs and reliable.rs commit a lock; netcode.rs does not" — framed as if this repo were the outlier, with the stated fix being to add one here.
That reading is backwards. This repo's
.gitignoreis hand-written and listsCargo.lockandfuzz/Cargo.lockbeside the fuzz artifacts. The other two never mention it, so their locks are committed by omission rather than by decision — and both are near-empty (1 and 2 packages) because those crates have essentially no dependencies. This is the only Rust port with real ones (57 packages via chacha20poly1305).So the considered choice is this one, and there is nothing to fix.
I had already run
cargo generate-lockfilehere before checking — which is exactly the failure the hot blocks exist to stop, attempted minutes after finishing them. The.gitignoreis what caught me, so the note goes where the next person hits it first.Also records that the lock is packaged into the published
.crate, so if this is ever revisited it is a version site, not just a dev-convenience question.🤖 Generated with Claude Code