Skip to content

Commit

Permalink
Fix test. The error message changed, but is still valid.
Browse files Browse the repository at this point in the history
We should really have only one way to say this,
I made a ticket: #633
  • Loading branch information
yav committed Jul 5, 2019
1 parent 4b5d569 commit ca4968f
Showing 1 changed file with 10 additions and 10 deletions.
20 changes: 10 additions & 10 deletions tests/issues/issue582.icry.stdout
Original file line number Diff line number Diff line change
@@ -1,19 +1,19 @@
Loading module Cryptol

[error] at <interactive>:1:1--1:18:
`inf` is not finite.
Expected a finite type, but found `inf`.

[error] at <interactive>:1:1--1:18:
`inf` is not finite.
Expected a finite type, but found `inf`.

[error] at <interactive>:1:1--1:16:
Unsolvable constraint: 0 >= 1

[error] at <interactive>:1:1--1:18:
`inf` is not finite.
Expected a finite type, but found `inf`.

[error] at <interactive>:1:1--1:18:
`inf` is not finite.
Expected a finite type, but found `inf`.

[error] at <interactive>:1:1--1:16:
Unsolvable constraint: 0 >= 1
Expand All @@ -28,15 +28,15 @@ Loading module Main
the following constraints hold:
• fin j
arising from
use of partial type function /^
use of partial type function (/^)
at ./issue582.cry:1:7--1:21
• fin i
arising from
use of partial type function /^
use of partial type function (/^)
at ./issue582.cry:1:7--1:21
• j >= 1
arising from
use of partial type function /^
use of partial type function (/^)
at ./issue582.cry:1:7--1:21
[error] at ./issue582.cry:5:1--5:11:
Failed to validate user-specified signature.
Expand All @@ -46,13 +46,13 @@ Loading module Main
the following constraints hold:
• fin j
arising from
use of partial type function %^
use of partial type function (%^)
at ./issue582.cry:4:7--4:21
• fin i
arising from
use of partial type function %^
use of partial type function (%^)
at ./issue582.cry:4:7--4:21
• j >= 1
arising from
use of partial type function %^
use of partial type function (%^)
at ./issue582.cry:4:7--4:21

0 comments on commit ca4968f

Please sign in to comment.