Check for --force-warn in Clippy's driver run condition

[xFrednet]

Just a thing I've noticed while tinkering on the driver. Currently, the driver only checks for --cap-lints=allow to determine if Clippy should run on the code, but ignores possible --force-warn arguments

---

changelog: Others: Allowing all lints and only --force-warning some will now work with Clippy's driver

[rust-highfive]

r? @dswij

(rust-highfive has picked a reviewer for you, use r? to override)

[dswij]

If I understand it correctly, will this change means that --force-warn clippy:: will completely precede --cap-lints allow?

[xFrednet]

Yes, the --force-warn flag is defined to warn, even if --cap-lints allow is set. --force-warn clippy:: will be accepted by that implementation, but should issue a warning, since clippy:: is not a valid lint name. The whole cap_lints_allow is just a test to safe performance for dependencies, AFAIK.

[dswij]

Makes sense. LGTM, thanks for this!

[xFrednet]

Thanks for the review! Is there anything else that needs to be done before the merge or did you forget to r+? 🙃

[dswij]

Oops, you're right 😅

@bors r+

[bors]

📌 Commit 4182803 has been approved by dswij

[bors]

⌛ Testing commit 4182803 with merge 3f47cd1...

[bors]

☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test
Approved by: dswij
Pushing 3f47cd1 to master...