bevy
bevy copied to clipboard
Enable warning for the `clippy::question_mark` lint
Objective
- Enable the
warnlevel for theclippy::question_marklint. It seems rather uncontroversial and general good practice to me.
Solution
- Enable the lint.
- Use the question mark/
okadapter to simplify someOption/Resultreturns. I can revert that and keep only the changes highlighted by the lint if preferable. - Fix some trailing whitespace.
There are two other question mark related lints that could be added alongside this one, which currently do not trigger anywhere in the codebase (unless we want to go with always one lint per PR):
One lint per PR is nice: it lets us evaluate the impact and discuss them seperately.
@mockersf do you still want to mark this PR as controversial?