misrefactored_assign_op's known problems wording
This commit is contained in:
Dale Wijnand 2018-07-24 09:26:28 +01:00
parent 6ad7a92ff8
commit 70f5bb1ff6
No known key found for this signature in database
GPG key ID: 4F256E3D151DF5EF

View file

@ -53,8 +53,8 @@ declare_clippy_lint! {
/// ///
/// **Known problems:** Clippy cannot know for sure if `a op= a op b` should have /// **Known problems:** Clippy cannot know for sure if `a op= a op b` should have
/// been `a = a op a op b` or `a = a op b`/`a op= b`. Therefore it suggests both. /// been `a = a op a op b` or `a = a op b`/`a op= b`. Therefore it suggests both.
/// If `a op= a op b` is really the correct behaviour then /// If `a op= a op b` is really the correct behaviour it should be
/// rewrite it as `a = (2 * a) op b` as it's less confusing. /// written as `a = a op a op b` as it's less confusing.
/// ///
/// **Example:** /// **Example:**
/// ```rust /// ```rust