[CHORE] use cargo-machete in pre-commit hook

[andrewgazelka]

questions:

• can we install it somehow? how about a pinned version?
• which order should it be in?
• am I doing this right? I am not familiar with pre-commit

[samster25]

This one is a bit tricky since this will require everyone who is developing in daft to have cargo machete installed on their machine. We can assume folks will have rust fmt and clippy installed but this might be a stretch!

One work around is to invoke a shell script for the hook that first checks if cargo machete is installed and prints out a warning on how to install it

[codspeed-hq]

CodSpeed Performance Report

Merging #2929 will not alter performance

_{Comparing andrew/pre-commit-machete (bd6b6e4) with main (62d0581)}

Summary

✅ 17 untouched benchmarks

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.31%. Comparing base (62d0581) to head (bd6b6e4).
Report is 74 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2929      +/-   ##
==========================================
- Coverage   78.32%   78.31%   -0.02%     
==========================================
  Files         602      602              
  Lines       71047    71047              
==========================================
- Hits        55648    55640       -8     
- Misses      15399    15407       +8     

see 6 files with indirect coverage changes

[andrewgazelka]

This one is a bit tricky since this will require everyone who is developing in daft to have cargo machete installed on their machine. We can assume folks will have rust fmt and clippy installed but this might be a stretch!

One work around is to invoke a shell script for the hook that first checks if cargo machete is installed and prints out a warning on how to install it

ba9adbb

should fix this