14/#100daysofcode made a case-insensitive BTreeMap lookup zero-copy, then fixed my first missing-Cargo.lock-related red build https://bitbucket.org/delan/nonymous/branches/compare/1d22c3b16dd45db6430a9cb47095472bc75bdfbe..d21cc4b831a1871c307cadda2ede26f4d8ebfdc5 …
-
Show this thread
-
#rustlang Cargo.lock in a nutshell 1. binaries heed them 2. libraries ignore them 3. one to a workspace so checking them into VCS is a. safe but useless for libraries b. necessary for workspaces with binaries https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries …3 replies 6 retweets 20 likesShow this thread -
Am I weird for thinking Cargo.lock is a misfeature and shouldn’t exist at all?
1 reply 0 retweets 1 like -
It’s how you get reproducible builds, which are very important!
1 reply 0 retweets 6 likes -
OK, but for that it should only ever need to exist as metadata attached to a binary package of some sort, shouldn’t it? having it associated with a source tree means people think it’s for controlling dependency versions, which is both dangerous and not the intention?
1 reply 0 retweets 0 likes
It is for controlling the versions; the ones you want for the project overall.
-
-
But that’s the exact thing that’s dangerous and people shouldn’t do.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.