1. 13 Jun, 2017 1 commit
    • Andrei Paskevich's avatar
      Eval_match: preserve quantifiers after passing to terms · 712dcd37
      Andrei Paskevich authored
      eval_match should not destruct user-written quantifiers.
      For this purpose it preserves all quantifiers inside annotations.
      For the same purpose it now also preserves all quantifiers appearing
      inside terms in let-bindings (in particular, inside lambdas).
      712dcd37
  2. 22 May, 2017 1 commit
  3. 29 Apr, 2017 2 commits
  4. 20 Apr, 2017 2 commits
  5. 16 Feb, 2017 2 commits
  6. 30 Jan, 2017 2 commits
  7. 29 Jan, 2017 4 commits
  8. 28 Jan, 2017 3 commits
  9. 23 Jan, 2017 1 commit
  10. 19 Jan, 2017 1 commit
  11. 15 Mar, 2016 1 commit
  12. 01 Mar, 2016 3 commits
  13. 24 Jan, 2016 1 commit
  14. 06 Oct, 2015 2 commits
    • David Hauzar's avatar
      Marking record fields that will not be shown in counterexample. · f0cdb661
      David Hauzar authored
      Record fields labeled with label model_trace:@hide_field will be not
      shown in counterexample.
      f0cdb661
    • David Hauzar's avatar
      Not appending "." to names of record fields in counterexamples. · da802d43
      David Hauzar authored
      Previously, "." was automatically appended to names stored in
      model_trace label when creating variables corresponding to record
      fields in eval_match and when projecting record fields in the
      transformation intro_projections_counterexmp. Now, this is not done
      and "." must be given in model_trace label of the projection or
      record field.
      
      The reason is that for SPARK, character different from "." (e.g., "'"
      needs to be sometimes appended.
      da802d43
  15. 08 Sep, 2015 1 commit
  16. 07 Sep, 2015 2 commits
  17. 04 Sep, 2015 1 commit
  18. 03 Sep, 2015 3 commits
    • David Hauzar's avatar
      Bugfix: instead of replacing original labels with new labels, new labels · 101ed70b
      David Hauzar authored
      were added to original labels.
      101ed70b
    • David Hauzar's avatar
      Prevent loosing labels while doing eval_match. · f4a22d69
      David Hauzar authored
      When eval_match creates new terms from original terms, all labels of
      the original terms are copied to the new terms. The exception are
      labels of the form "model_trace:*". These labels are not copied if both
      original terms and new terms contain this label.
      f4a22d69
    • David Hauzar's avatar
      Traceability for record field names in counterexamples. · b25b6a72
      David Hauzar authored
      In wp, eval_match is used to replace record fields with simple variables
      of the same type. Originally, all labels from the variable that field
      was accessed were copied to new variables representing fields of this
      variable. Therefore also "model_trace:var_name" label was copied and thus
      the field had name "var_name" in the counterexample.
      
      This commit solves this problem by appending names of the fields to
      "model_trace:*" label of new variables representing record fields.
      b25b6a72
  19. 20 Mar, 2015 1 commit
  20. 19 Mar, 2015 1 commit
  21. 05 Mar, 2015 1 commit
  22. 11 Jul, 2014 1 commit
    • Martin Clochard's avatar
      Hack to prevent eval-match from decomposing quantified records · 698ca990
      Martin Clochard authored
        This is to prevent quantified records from being decomposed by
        eval_match. e.g, assert { forall x:t. ... } was previously
        transformed to assert { forall x1:t1, x2:t2, x3:t3. ... } if x was
        a record type with fields x1,x2,x3. This changed the
        instantiation pattern, which could be harmful.
      698ca990
  23. 14 Mar, 2014 1 commit
  24. 18 Jan, 2014 1 commit
  25. 10 Nov, 2013 1 commit