1. 22 Feb, 2016 1 commit
  2. 05 Feb, 2016 1 commit
    • Andrei Paskevich's avatar
      Mlw_expr: fix potentially unsound pattern matching in programs · 2d1a5883
      Andrei Paskevich authored
      split the ppat_ghost field in program patterns into two distinct
      conditions:
      - ppat_ghost, indicating that the pattern starts as ghost,
        meaning that all variables in it are ghost, too;
      - ppat_fail, meaning that the pattern contains a refutable
        ghost subpattern, which makes the match in the extracted code
        impossible, which makes the whole match expression ghost.
      
      Until now, the two conditions were disjunctively combined, making
      admissible the invalid pattern matching in bench/p/b-d/ghost4.mlw.
      2d1a5883
  3. 10 Jan, 2016 1 commit
    • Andrei Paskevich's avatar
      Mlw_expr: fix potentially unsound pattern matching in programs · eda92a0b
      Andrei Paskevich authored
      split the ppat_ghost field in program patterns into two distinct
      conditions:
      - ppat_ghost, indicating that the pattern starts as ghost,
        meaning that all variables in it are ghost, too;
      - ppat_fail, meaning that the pattern contains a refutable
        ghost subpattern, which makes the match in the extracted code
        impossible, which makes the whole match expression ghost.
      
      Until now, the two conditions were disjunctively combined, making
      admissible the invalid pattern matching in bench/p/b-d/ghost4.mlw.
      eda92a0b
  4. 03 Jul, 2015 1 commit
  5. 17 Feb, 2015 1 commit
  6. 12 Feb, 2015 1 commit
  7. 22 Sep, 2014 1 commit
  8. 11 Sep, 2014 1 commit
  9. 10 Sep, 2014 1 commit
  10. 31 Aug, 2014 2 commits
  11. 21 Aug, 2014 1 commit
  12. 02 Jun, 2014 1 commit
  13. 28 May, 2014 1 commit
  14. 11 Mar, 2014 1 commit
  15. 09 Mar, 2014 1 commit
  16. 04 Mar, 2014 2 commits
  17. 27 Feb, 2014 1 commit
  18. 25 Feb, 2014 1 commit
  19. 21 Feb, 2014 2 commits
  20. 16 Feb, 2014 1 commit
  21. 15 Feb, 2014 2 commits
  22. 14 Feb, 2014 1 commit
  23. 03 Feb, 2014 4 commits
  24. 28 Jan, 2014 1 commit
  25. 21 Jan, 2014 1 commit
  26. 20 Jan, 2014 1 commit
    • Andrei Paskevich's avatar
      WhyML: add "diverges", "reads {}", and "writes {}" effect clauses · 83858597
      Andrei Paskevich authored
      - "diverges" states that the computation may not terminate (which
        does not mean that is always diverges: just as any other effect
        annotation, this clause states a possibility of a side effect).
      
      - "reads {}" states that the computation does not access any variable
        except those that are listed elsewhere in the specification (or the
        proper function arguments, if "reads" is in a function spec).
      
      - "writes {}" states that the computation does not modify any mutable
        value.
      
      - If a function definition or an abstract computation may diverge,
        but there is no "diverges" clause in the specification, a warning
        is produced. If a function definition or an abstract computation
        always terminates, but there is a "diverges" clause in the spec,
        an error is produced.
      
      - If there is a "reads" or a "writes" clause in a function definition
        or an abstract computation, then every modified value must be listed
        in "writes" and every accessed external variable not mentioned in
        the spec must be listed in "reads". (Notice that this is a stricter
        requirement than before, when the presence of a "writes" clause
        did not require to specify "reads".) However, one does not have to
        write "reads {}" or "writes {}" if the corresponding lists are empty.
      83858597
  27. 19 Jan, 2014 1 commit
  28. 16 Jan, 2014 2 commits
  29. 15 Jan, 2014 2 commits
  30. 14 Jan, 2014 2 commits