1. 28 Nov, 2018 2 commits
    • Sylvain Dailler's avatar
      Removes model_trace added at parsing · 786526f4
      Sylvain Dailler authored
      Removes debug flag: debug_auto_model.
      Some changes in counterexamples triggered by:
      - (non counterexamples) transformations which have a specific case for
         model_trace but not for the new detection: this is intended as
         simplifications that would be done are often simplifications we want
         for counterexamples,
      - Some locations are missing in variables introduced by SP/WP which should
        explain the rest.
      
      This also disables projections for record in intro_projection_counterexmp.
      
      Correct subst_filter to be consistent with new counterexample modification
      786526f4
    • MARCHE Claude's avatar
      Avoid polymorphism · b6e01c68
      MARCHE Claude authored
      b6e01c68
  2. 27 Nov, 2018 1 commit
  3. 16 Nov, 2018 2 commits
  4. 06 Nov, 2018 1 commit
  5. 30 Oct, 2018 1 commit
  6. 29 Oct, 2018 1 commit
  7. 26 Oct, 2018 1 commit
  8. 24 Oct, 2018 2 commits
  9. 23 Oct, 2018 1 commit
  10. 22 Oct, 2018 8 commits
  11. 19 Oct, 2018 1 commit
  12. 11 Oct, 2018 1 commit
  13. 10 Oct, 2018 2 commits
  14. 05 Oct, 2018 1 commit
  15. 04 Oct, 2018 1 commit
  16. 02 Oct, 2018 1 commit
  17. 28 Sep, 2018 2 commits
  18. 26 Sep, 2018 1 commit
  19. 25 Sep, 2018 1 commit
  20. 23 Sep, 2018 1 commit
  21. 18 Sep, 2018 1 commit
  22. 12 Sep, 2018 1 commit
  23. 11 Sep, 2018 1 commit
    • Guillaume Melquiond's avatar
      Remove handcrafted error messages (fix issues #150 and #172). · ce21b6c1
      Guillaume Melquiond authored
      Short story: it was a source of bugs, there was only one handcrafted
      message over 650, and, to quote François Pottier, "you seem to have
      misunderstood what the various commands do".
      
      Long story: the proper steps to update the error messages after modifying
      the parser are
      
      1. update the old states with --update-errors
      2. generate the new states with --list-errors
      3. compare the old and new states with --compare-errors
      4. manually reconcile the differences between the old and new states
      5. write error messages for the new states
      6. add %on_error_reduce and go back to step 1, if step 5 is too hard
      7. check that the error messages for the old states are still meaningful
      8. check that the set of states is both correct (--compile-errors) and
         complete (--compare-errors)
      
      We were doing only step 1 and half of step 8. Doing the other half of
      step 8 would have prevented issue #172 from occurring. But that would have
      meant doing step 4 after each parser modification, which was never done.
      Note that step 2 is so expensive that it is impossible to perform step 8
      during continuous integration.
      
      Given the work needed to update the error messages after a syntax change,
      I don't think we can reliably use them until WhyML no longer evolves.
      ce21b6c1
  24. 05 Sep, 2018 1 commit
  25. 30 Aug, 2018 1 commit
  26. 12 Jul, 2018 3 commits