You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the JSON log of dafny measure-complexity --isolated-assertions, are vcResults assigned a vcNum according to their verification order? For example, is vcNum 1 verified before vcNum 2?
Asking because I have a log that lists the vcNums of the vcResults of a verificationResult out of order. E.g., I'm seeing a vcResult list with vcNums [4,1,3,2] in the JSON. So I wonder if they are being verified in JSON order or in vcNum order. This is important because, IIUC, if e.g. vcNum 3 fails verification, then subsequent verifications are unreliable.
When those example vcNums are sorted as [1,2,3,4], their line:col follow the order one encounters when reading the source code. This is the order that I intuitively (naively?) expected for verification. However some languages change the order of evaluation of things; so I wonder how this works during Dafny's verification.
What change in documentation do you suggest?
In the JSON log of
dafny measure-complexity --isolated-assertions
, arevcResults
assigned avcNum
according to their verification order? For example, isvcNum
1 verified beforevcNum
2?Asking because I have a log that lists the
vcNum
s of thevcResults
of averificationResult
out of order. E.g., I'm seeing avcResult
list withvcNums
[4,1,3,2] in the JSON. So I wonder if they are being verified in JSON order or invcNum
order. This is important because, IIUC, if e.g.vcNum
3 fails verification, then subsequent verifications are unreliable.When those example
vcNum
s are sorted as [1,2,3,4], their line:col follow the order one encounters when reading the source code. This is the order that I intuitively (naively?) expected for verification. However some languages change the order of evaluation of things; so I wonder how this works during Dafny's verification.Issue #5805 also made me think of this.
The text was updated successfully, but these errors were encountered: