vendor + linecount unfortunately doesn't represent an accurate number of what cargo-watch would actually use. It includes all platform specific code behind compile time toggles even though only one would be used at any particular time, and doesn't account for the code not included because the feature wasn't enabled. https://doc.rust-lang.org/cargo/reference/features.html
whether those factors impact how you view the result of linecount is subjective
also as one of the other commenters mentioned, cargo watch does more than just file watching
Your quote omits the portion where Dan explicitly addressed that case. It needs to be one year since it received “significant attention,” and also major new development. Dan’s post could be worded more clearly, though.
(We’re pretty far in the weeds here, but as long as we’re here – for all intents and purposes, this is a show HN.)
Good point - I just linked to the first relevant explanation. pvg linked to a much longer explanation that isn’t specific to, or about, Show HN: https://news.ycombinator.com/item?id=23071428
Super interesting proposal from David who is working on the wild linker. Sort of inverting the compilation process to drive codegen by what is actually needed, as opposed to compiling everything then throwing away what you don't need later.
The duplicate function checker tool is nifty too, 9% of my release build is duplicate functions. As mentioned in the article there are ways to bring this down if you can accept the trade offs.
aside: find it funny (genuinely), you describe this as "pretty easy" xD. ffmpeg is so impressive but so daunting from a cli perspective to me. how do you even know whats possible! I would never have imagined it could generate palettes
whether those factors impact how you view the result of linecount is subjective
also as one of the other commenters mentioned, cargo watch does more than just file watching
reply