mirror of
https://github.com/idris-lang/Idris2.git
synced 2024-12-20 18:21:47 +03:00
d531cc8dea
* Add field for universe level to TType This doesn't do anything yet, other than introduce new universe variables whenever we introduce a new type, but it's the first step towards checking the universe hierarchy. Next step is to add constraints when checking pi, unifying/converting types, and when adding data constructors. * TTC version increment Thought I'd done this, but apparently I didn't save the file. Oops! * Add structure for universe constraints * Fix display of ambiguity errors We need to store the Context in errors at the point where the error occurs, or we might get some nonsense in the message. There's still a couple of places in Error where we don't do this right. This fixes one of them, and improves a few messages in the process.
16 lines
743 B
Plaintext
16 lines
743 B
Plaintext
Processing as TTImp
|
|
Written TTC
|
|
Yaffle> Bye for now!
|
|
Processing as TTImp
|
|
Dot2:15:1--16:1:When elaborating left hand side of Main.half:
|
|
Dot2:15:28--15:30:Pattern variable {P:n:393} unifies with ?{P:m:393}_[]
|
|
Yaffle> Bye for now!
|
|
Processing as TTImp
|
|
Dot3:18:1--19:1:When elaborating left hand side of Main.addBaz3:
|
|
Dot3:18:10--18:15:Can't match on ($resolved365 ?{P:x:404}_[] ?{P:x:404}_[]) (Not a constructor application or primitive) - it elaborates to ($resolved365 ?Main.{_:53}_[] ?Main.{_:54}_[])
|
|
Yaffle> Bye for now!
|
|
Processing as TTImp
|
|
Dot4:17:1--18:1:When elaborating left hand side of Main.addBaz4:
|
|
Dot4:17:33--17:34:Can't match on ?{P:x:406}_[] (Non linear pattern variable) - it elaborates to ?Main.{dotTm:55}_[]
|
|
Yaffle> Bye for now!
|