summaryrefslogtreecommitdiff
path: root/Test/dafny0/Superposition.dfy.expect
Commit message (Collapse)AuthorAge
* Fix: Unify column numbers in Dafny's errorsGravatar Clément Pit--Claudel2015-07-23
| | | | | | | | | Dafny counts from 0, but Boogie counts from 1. Tokens are 1-based. Thus when we print tokens, we need to decrement the column number. This was done for resolver errors, but not for verification or parsing errors. In addition, parsing errors were inconsistent with resolution errors case-wise. Unfortunately, the fix affects the output of many tests.
* Postpone reads checks of function preconditions until after the entire ↵Gravatar leino2015-06-15
| | | | precondition has otherwise been checked for well-formedness
* Combined some common routines into CheckWellformedAndAssume, which also ↵Gravatar leino2015-06-12
| | | | allows an improvement of the generated Boogie (which will be especially good soon, when reads-clause checking may change)
* This changeset changes the default visibility of a function/predicate body ↵Gravatar leino2015-03-09
| | | | | | | | | | outside the module that declares it. The body is now visible across the module boundary. To contain the knowledge of the body inside the module, mark the function/predicate as 'protected'. Semantics of 'protected': * The definition (i.e., body) of a 'protected' function is not visible outside the defining module * The idea is that inside the defining module, a 'protected' function may or may not be opaque. However, this will be easier to support once opaque/reveal are language primitives. Therefore, for the time being, {:opaque} is not allowed to be applied to 'protected' functions. * In order to extend the definition of a predicate in a refinement module, the predicate must be 'protected' * The 'protected' status of a function must be preserved in refinement modules
* New logical encoding of types with Is and IsAllocGravatar Dan Rosén2014-07-07
|
* Set up the same test infrastructure as in Boogie.Gravatar wuestholz2014-05-29