4 commits

Author	SHA1	Message	Date
Leonardo de Moura	5d3f0606d2	feat: include type of type in "mismatch errors" ... @Kha we do that in Lean 3. It helps when the error is due to incorrect universe levels. BTW, I had to update `tests/lean/server/content_diag.json` since the error message is different, but a few other stuff changed too. Could you please take a look whether the test is still correct?	2021-03-08 09:30:34 -08:00
Sebastian Ullrich	b2b78eb222	test: use printMessageEndPos for leantests	2021-01-15 16:27:59 +01:00
Leonardo de Moura	d2cdef85ea	chore: fix tests	2021-01-14 14:25:41 -08:00
Leonardo de Moura	06ad52575a	feat: force users to use discard when action result is not being bound and it is not PUnit ... After this commit, we have to use an explicit `discard` in code such as ``` def g (x : Nat) : IO Nat := ... def f (x : Nat) : IO Unit := do discard <| g x -- type error without the `discard` IO.println x ``` Motivation: prevent users from making mistakes such as ``` def f (xs : Array Nat) : IO Unit := do xs.set! 0 1 IO.println xs ``` when they meant to write ``` def f (xs : Array Nat) : IO Unit := do let xs := xs.set! 0 1 IO.println xs ```	2020-12-08 06:14:48 -08:00