Conversation
shlex has tests to test shlex, we can trust the shlex tests to test shlex properly.
the compailer will fail if these are traits are not implemented anyways
📝 WalkthroughWalkthroughThe change removes obsolete command-line parsing and ChangesCommand Test Cleanup
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
I think I considered dropping those much earlier, but decided against them because shlex tests might still fail without us knowing. If shlex tests fail, we don't realize they do, and get affected by a regression on an update we'll have no way to trace the error (unless we decide to look at shlex itself) and we'll have no early-indicators. |
shlex has tests to test shlex, we can trust the shlex
tests to test shlex properly.
same with the other tests, we'll get a compiler error if these traits are not implemented.
Sanity Checking
nix fmtto format my Nix codecargo fmtto format my Rust codecargo clippyand fixed any new linter warnings.logic
description.
x86_64-linuxaarch64-linuxaarch64-darwinAdd a 👍 reaction to pull requests you find important.