You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some linters and tidiers implement their own caching, could that be leveraged? Would it be worth the hassle of keeping track of which ones did vs didn't? Does cargo fmt do any caching detection I wonder?
You've got me thinking about the adage that all projects end up as either an email client or a poor re-implementation of Make.
At a minimum threshold, this will need to work better than make -j ... would work, assuming that the linter and tidier dropped some sort of stub output for the make rules. (Implementing checksums would automatically pass that bar.)
Caching tidy/lint checks between runs would be great.
Some things to think about ...
Caching should be per filter and then per file/dir.
The cache key should include file (or dir) checksum, precious binary checksum, filter config, and checksum of the filter's binary.
The text was updated successfully, but these errors were encountered: