on master help sign in
Do not use the term "arguments" in binary operator errors
commit5bf3d0cba6f31b4084b87473f229fd3244b3ac1c authorEvan Czaplicki <evancz@users.noreply.github.com> dateMon 8 Aug 2016, 16:00 (10 years ago) parent22bbeae
1 file changed+5−5
src/Reporting/Error/Type.hs+5−5
src/Reporting/Error/Type.hs+5−5
@@ -261,14 +261,14 @@ mismatchToReport localizer (MismatchInfo hint leftType rightType maybeReason) =
261261 BinopRight op region ->
262262 report
263263 (Just region)
264− ("The right argument of " ++ prettyName op ++ " is causing a type mismatch.")
264+ ("The right side of " ++ prettyName op ++ " is causing a type mismatch.")
265265 ( cmpHint
266− (prettyName op ++ " is expecting the right argument to be a:")
267− "But the right argument is:"
266+ (prettyName op ++ " is expecting the right side to be a:")
267+ "But the right side is:"
268268 ( binopHint op leftType rightType
269269 ++
270− [ "I always figure out the type of the left argument first and if it is\
271− \ acceptable on its own, I assume it is \"correct\" in subsequent checks.\
270+ [ "With binary operations, I always figure out the left side first. If it\
271+ \ seems fine, I assume it is \"correct\" in subsequent checks.\
272272 \ So the problem may actually be in how the left and right arguments interact."
273273 ]
274274 )