1. 02 Jul, 2018 1 commit
  2. 15 Jun, 2018 2 commits
  3. 14 Jun, 2018 1 commit
  4. 07 Feb, 2018 1 commit
  5. 12 Jan, 2018 1 commit
  6. 15 Dec, 2017 2 commits
  7. 07 Nov, 2017 1 commit
  8. 19 Oct, 2017 1 commit
  9. 11 Oct, 2017 1 commit
  10. 19 Jul, 2017 1 commit
  11. 29 Jun, 2017 1 commit
  12. 21 Jun, 2017 1 commit
  13. 16 Jun, 2017 1 commit
    • Andrei Paskevich's avatar
      WhymL: break and continue · df239061
      Andrei Paskevich authored
      Without an argument, break and continue refer to the innermost loop.
      A label put over an expression sequence starting with a loop, can be
      used as an optional argument for break and continue:
      
        label L in
        [ghost] ["tag"] [M.begin]
          while true do
            ...
            break L
            ...
          done;
          [...]
        [end] [: unit]
      
      In the square brackets are listed the constructions allowed between
      the label declaration and the loop expression.
      df239061
  14. 31 May, 2017 1 commit
  15. 15 May, 2017 1 commit
  16. 12 May, 2017 1 commit
  17. 20 Apr, 2017 2 commits
  18. 28 Jul, 2016 1 commit
  19. 31 Mar, 2016 1 commit
  20. 24 Mar, 2016 1 commit
  21. 23 Mar, 2016 1 commit
  22. 21 Mar, 2016 2 commits
  23. 09 Mar, 2016 2 commits
  24. 20 Aug, 2015 1 commit
    • Andrei Paskevich's avatar
      adapt the standard library · cb9aa0a2
      Andrei Paskevich authored
      except for modules/impset.mlw (because of Fset) and modules/mach/*
      (because of program cloning), the standard library now typechecks.
      
      This is still very much the work in progress. Many functions and
      predicates have still to be converted to "let function" and
      "let predicate". Here are some TODOs:
      - do not require the return type for "val predicate", "val lemma", etc.
      - do not require explicit variant for "let rec" if the code passes
        the termination check in Decl (see list.why)
      - what should become "val ghost function" and what should stay just
        "function" (see array.mlw, matrix.mlw, string.mlw, etc)?
      - some defined functions in algebra.why and relations.why had to be
        removed, so that they can be implemented with "let function" in
        int.mlw (since they are defined, they cannot be instantiated with
        let-functions). This seems too restrictive. One way out would be
        to authorise instantiation of defined functions (with a VC).
      - should we keep the keyword "model"? reuse of "abstract" in types
        breaks syntax coloring ("abstract" requires closing "end" in
        programs but not in types; maybe we can drop that "end" again?).
      cb9aa0a2
  25. 06 Jul, 2015 1 commit
  26. 01 Jul, 2015 1 commit
  27. 24 Nov, 2014 1 commit
  28. 23 Nov, 2014 1 commit
  29. 08 Jun, 2014 1 commit
  30. 29 Mar, 2014 1 commit
  31. 28 Mar, 2014 1 commit
  32. 25 Feb, 2014 1 commit
  33. 24 Feb, 2014 1 commit
    • Jean-Christophe Filliatre's avatar
      library: map.MapPermut now defined using map.Occ · ca0ec4aa
      Jean-Christophe Filliatre authored
      (that is, using number of occurrences)
      No more definition of permutation using inductive predicates.
      Impacts array.ArrayPermut; proof sessions updated.
      Coq realizations for map.Occ and map.MapPermut;
      proof session for array.ArrayPermut in progress
      ca0ec4aa
  34. 14 Feb, 2014 1 commit
  35. 12 Feb, 2014 1 commit