Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Use file hashes instead of modification time for tracking changes #502
As mentioned in this email thread, switching branches, using git stash, rebasing and other operations cause lots of rebuilds, since they change the modification time of files. On the other hand, switching to a branch and back shouldn't require any rebuilds, since the sources haven't changed.
To fix this, stack could track the hash of the input files to detect changes. To make this perform, this should probably only be checked after the modification time and file size are different, as @ndmitchell mentions shake does in the email thread.
1 similar comment
I just thought of one possible downside to this: I can picture bug reports coming in of "I ran
added a commit
Jul 3, 2015
Awesome! I'm still dissatisfied with the null builds being so long (though on large projects, that may be necessary). We have more optimizing to do in the future.
This also fixed a bug I had on a client project, so I'm quite happy with it. We'll cut a release to include this on Sunday.