1. 17 Apr, 2015 11 commits
  2. 16 Apr, 2015 2 commits
  3. 15 Apr, 2015 8 commits
  4. 14 Apr, 2015 1 commit
  5. 13 Apr, 2015 6 commits
  6. 12 Apr, 2015 2 commits
  7. 11 Apr, 2015 2 commits
    • Andrei Paskevich's avatar
      examples/vstte10_queens: strong updates · 340ffc11
      Andrei Paskevich authored
      1. Strong region updates can only work with direct assignments, e.g.
           r.contents <- something_completely_different
         but not with functions such as (:=) : ref 'a -> 'a -> unit
         Why3 requires 'a to be instantiated with one concrete type,
         not with a bunch of types that differ in their regions.
      2. Strong region updates will restrict the updated regions to their
         covers. However, in the current implementation, Why3 does not know
         if the region corresponding to the field "contents" is the only
         cover for 'a in the type [ref 'a] or if there is a way to retrieve
         'a from [ref 'a] without going through "contents". Therefore, to
         ensure soundness, a strong update of r.contents will forbid to
         use r itself. A solution consists in writing an adhoc "reference"
         type, where the mutable contents (O.t in this case) is explicitly
         given in the type definition. Then the strong update of the field
         containing O.t will preserve the covering "reference".
         This problem is fixed in the "new system", where mutable types
         carry information about the access paths of the type variables.
         There, "r.contents <- something_different" preserves r.
    • Jean-Christophe Filliâtre's avatar
  8. 10 Apr, 2015 2 commits
  9. 09 Apr, 2015 1 commit
  10. 08 Apr, 2015 5 commits