on master help sign in
remove TODO about checking error message quality

I think this is in reference to using "parentheses vs tuple" language, where I wasn't 100% sure it was safe to say tuple even though that'd probably be good. I think it's alright as is though.

commit8606d647981185b7d3b874a72afc214558c90bd3 authorEvan Czaplicki <evancz@users.noreply.github.com> dateFri 28 Jun 2019, 12:07 (7 years ago) parentdcbe51f
1 file changed−1
compiler/src/Reporting/Error/Syntax.hs−1
compiler/src/Reporting/Error/Syntax.hs−1
@@ -2243,7 +2243,6 @@ toExprReport source context expr startRow startCol =
22432243 InNode NElse r c _ -> (r, c, "an `if` expression")
22442244 InNode NCase r c _ -> (r, c, "a `case` expression")
22452245 InNode NBranch r c _ -> (r, c, "a `case` expression")
2246− -- TODO check if this is actually the best way to get error messages here
22472246
22482247 surroundings = A.Region (A.Position contextRow contextCol) (A.Position row col)
22492248 region = toRegion row col