1. 23 Jan, 2017 1 commit
  2. 20 Jan, 2017 2 commits
  3. 19 Jan, 2017 2 commits
  4. 01 Jan, 2017 1 commit
  5. 18 Aug, 2016 1 commit
  6. 21 Mar, 2016 1 commit
  7. 17 Mar, 2016 1 commit
  8. 15 Mar, 2016 3 commits
  9. 05 Mar, 2016 2 commits
  10. 25 Feb, 2016 1 commit
  11. 24 Feb, 2016 1 commit
  12. 22 Feb, 2016 1 commit
  13. 11 Feb, 2016 1 commit
  14. 09 Feb, 2016 1 commit
  15. 24 Jan, 2016 1 commit
  16. 17 Jan, 2016 1 commit
  17. 11 Jan, 2016 1 commit
    • Andrei Paskevich's avatar
      Mlw: non-ghost unit expressions have MaskVisible · e12222bc
      Andrei Paskevich authored
      This makes "let f ... : unit = <effect> ; <ghost effect>" acceptable
      without ghostness annotation in the result.
      However, "let f ... : unit = <ghost effect>" is still required to
      be marked ghost (unless f is a local non-recursive function).
  18. 10 Jan, 2016 1 commit
    • Andrei Paskevich's avatar
      Mlw: allow non-ghost expressions to return (partially) ghost values · 4c79348a
      Andrei Paskevich authored
      this is still work in progress and no testing was done so far.
      Highlights of this commit:
      - "(ghost 42, 15)" is now a non-ghost expression that can be returned
        from a function and/or matched against a "(ghost x, y)" pattern.
        Only the tuple constructor and direct pattern matching are magical:
        "let z = (ghost 42, 15) in ..." still makes z ghost, and therefore
        "snd (ghost 42, 15)" is ghost, too.
      - "if c then e1 else ghost e2" and "let z = e1 in ghost e2" are now
        non-ghost expressions with a ghost result. This means that e1 may
        have visible effects. Of course, if e2 raises exceptions, the whole
        expression is ghostified. Contamination is still done when possible,
        that is, when the contaminated expression has no visible effects.
      - "let ghost x = e1 in e2" no longer ghostifies e1.
      - "let f (ghost x) = ... in f e1" no longer ghostifies e1.
      - new syntax: variables in program patterns may be marked ghost.
        In particular: "let x, ghost y = ...".
      - new syntax: the function result type may be written as a partially
        ghost tuple: "val f ... : ghost int" or "any (int, ghost bool)".
        The ghostness annotation is required for top-level and recursive
      - exceptions can carry partially ghost tuples (API only, WIP)
  19. 07 Dec, 2015 2 commits
  20. 30 Nov, 2015 1 commit
  21. 24 Nov, 2015 1 commit
  22. 15 Nov, 2015 1 commit
    • Andrei Paskevich's avatar
      Mlw: admit fields with mutable types in private records · f522e56e
      Andrei Paskevich authored
      this should not be problematic as long as these fields do not occur
      in the invariants (actual or refined). In other words, a value of
      a private type exists no matter what is stored in the field.
      Also, admit non-private mutable types without actual mutable fields.
      It is actually impossible to create a write effect for such types,
      and the only consequence of being mutable is that they are assigned
      a region, and so every value of such type can be tracked individually.
      One use case for this is a non-private record with an invariant,
      which either has fields with mutable types or has type parameters
      that we wish to instantiate with mutable types. If we modify these
      mutable components, this may break the record's invariant. Now, if
      the record itself is immutable (and thus has no associated region),
      then we must reestablish the invariant immediately, otherwise we
      lose track of the value. Even if this extra flexibility does not
      prove useful in the end, it seems to be harmless.
      Also, admit type definitions of the form
        type t 'a = (private|abstract)? mutable? {} invariant*
      which define private empty records (even if not declared private).
      Also, "type t 'a" is now equivalent to "type t 'a = private {}".
  23. 13 Nov, 2015 1 commit
  24. 10 Nov, 2015 1 commit
  25. 08 Nov, 2015 1 commit
  26. 22 Aug, 2015 1 commit
  27. 20 Aug, 2015 1 commit
    • Andrei Paskevich's avatar
      HighOrd is new Map · 402fa65b
      Andrei Paskevich authored
      0. define Map.map 'a 'b as an alias 'a -> 'b
      1. define Set.set as an alias for 'a -> bool
      2. rename HighOrd.func to (->)
      3. remove HighOrd.pred
      4. update drivers
  28. 01 Aug, 2015 1 commit
    • Andrei Paskevich's avatar
      Ity: another revision of eff_assign · d1453b19
      Andrei Paskevich authored
      in this version, we reconstruct and scan the mutable fields of all
      regions that occur in an assignment, independently on whether the
      region is modified. This avoids a bug in the previous version where
      the "left" and "right" subregion lists could have different length.
      This also avoids a bug in the version before that, where an upper
      region could have a shorter subregion list than one of its subregions.
      It is possible to fix those issues in a more efficient manner, but this
      seems to make code quite more complex for a non-existent practical gain.
  29. 31 Jul, 2015 2 commits
  30. 30 Jul, 2015 1 commit
    • Léon Gondelman's avatar
      Ity: resets are protected by a common set of covers · faf9a2be
      Léon Gondelman authored
      The effects now must satisfy the following invariants:
      1. Every region in eff_writes, eff_taints, and eff_covers
         must occur in the type of some variable in eff_reads.
      2. Both eff_taints and eff_covers are subsets of eff_writes.
      3. eff_covers and eff_resets are disjoint.
      4. Every region in eff_writes is either in eff_covers or
         is stale (according to Ity.reg_r_stale) and forbidden
         for the later use.
      Also, this commit rewrites Ity.eff_assign and Ity.eff_strong
      (renamed now to eff_reset_overwritten) to handle correctly
      parallel assignments.
  31. 17 Jul, 2015 1 commit
  32. 02 Jul, 2015 1 commit
  33. 27 Jun, 2015 1 commit