Login
You're viewing the techdon.dev public feed.

Replies

  • Sep 3, 2026, 12:23 PM

    @epage does this take a checksum of the whole file or does it ignore things like comments? i often change something irrelevant while i already started a build and when i do e.g another cargo run later it wants a rebuild even though i still didnt change anything besides comments/whitespace ;_;

    💬 1🔄 0⭐ 0
  • Sep 3, 2026, 12:32 PM

    @cabinentaxi The whole file.

    I saw that build2 ignores whitespace / non-semantic comments so long as they don't change spans of regular tokens but held off on the complexity of that since not changing spans seems niche, there is incremental compilation which should help, and other efforts like relink-don't-rebuild should help even further.

    That said, it is something we can add in the future.

    💬 0🔄 0⭐ 0
  • Sep 4, 2026, 7:57 PM

    @epage The case I keep hitting is a build box that restores target/ from a cache and checks the source out fresh, so every mtime is newer than every artifact and the whole tree rebuilds. Content checksums are the fix for that, and it is a more common setup than the mtime model assumes. Glad to see it heading for stable.

    💬 1🔄 0⭐ 0
  • Sep 4, 2026, 11:33 PM

    @emillindfors The one caveat is this won't help for local build scripts because the existing interface isn't safe against race conditions with checksums.

    💬 1🔄 0⭐ 0
  • Sep 6, 2026, 2:12 PM

    @epage Good to know, and it still covers my case: the cache-restore box never touches the sources after checkout, so the compilation units are where the rebuilds come from. Does a crate with rerun-if-changed just stay on mtimes for those paths after stabilisation, with the rest of the graph on checksums?

    💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0