Une MAJ de sécurité est nécessaire sur notre version actuelle. Elle sera effectuée lundi 02/08 entre 12h30 et 13h. L'interruption de service devrait durer quelques minutes (probablement moins de 5 minutes).

  1. 20 Jul, 2012 1 commit
  2. 18 Jul, 2012 3 commits
  3. 17 Jul, 2012 2 commits
  4. 16 Jul, 2012 1 commit
    • Andrei Paskevich's avatar
      whyml: several API simplifications · 9b75e276
      Andrei Paskevich authored
      - get rid of val_decl, the psymbol/pvsymbol is enough
      - get rid of vtv_vars, keep the varset in pvsymbol
      - include fresh regions in pd_news (will serve for clone)
      9b75e276
  5. 14 Jul, 2012 2 commits
  6. 12 Jul, 2012 1 commit
  7. 11 Jul, 2012 1 commit
  8. 08 Jul, 2012 1 commit
  9. 07 Jul, 2012 1 commit
  10. 04 Jul, 2012 1 commit
  11. 28 Jun, 2012 2 commits
    • Andrei Paskevich's avatar
      whyml: include pure symbols in the program namespace · 55c1fc02
      Andrei Paskevich authored
      Thus, we do not need to look through two different namespaces.
      The only difference w.r.t. the core namespace semantics is that
      a program symbol (pvsymbol, psymbol, plsymbol, or xsymbol) may
      be introduced in the scope of an lsymbol of the same name and
      overshadow it in program expressions, though not in specifications.
      For example, the following declarations allow to use (!) both in
      programs and specifications:
      
          type ref 'a = {| mutable contents : 'a |}
          function (!) (x: ref 'a) : 'a = x.contents
          let (!) (r: ref 'a) = {} r.contents { result = !r }
      
      Notice, however, that itsymbols cannot overshadow pure tsymbols.
      55c1fc02
    • Andrei Paskevich's avatar
      a384381e
  12. 24 Jun, 2012 2 commits
    • Andrei Paskevich's avatar
      whyml: do not count the used symbols in program declarations · d7477cf4
      Andrei Paskevich authored
      It is difficult to count all the used symbols in programs.
      On the other hand, the pure API already cares about the missing
      symbols in verification conditions. So we relieve the program API
      of this duty, and trust typechecking (and any other API user) to
      not forget to add all the necessary dependencies to a module.
      
      The worst possible outcome, it seems, is that one can extract
      an ill-formed OCaml code if the WhyML module is done via the API,
      and VCs were not generated.
      d7477cf4
    • Andrei Paskevich's avatar
      whyml: handle abstract types · 724fd017
      Andrei Paskevich authored
      724fd017
  13. 23 Jun, 2012 1 commit
  14. 17 Jun, 2012 2 commits
  15. 10 Jun, 2012 2 commits
  16. 30 May, 2012 1 commit
  17. 22 May, 2012 1 commit
  18. 07 May, 2012 1 commit
  19. 26 Apr, 2012 1 commit
  20. 25 Apr, 2012 1 commit
  21. 09 Apr, 2012 1 commit
  22. 18 Mar, 2012 1 commit
    • Andrei Paskevich's avatar
      separate abstract types and logic symbols · 1b769a78
      Andrei Paskevich authored
      - put abstract types and aliases in Dtype of tysymbol
      - put (recursive) algebraic types in Ddata of (ts,constr list) list
      - put abstract function/predicate symbols in Dparam of lsymbol
      - put defined logic symbols in Dlogic of (ls,ls_definition) list
      1b769a78
  23. 29 Feb, 2012 1 commit
  24. 26 Feb, 2012 1 commit
  25. 24 Feb, 2012 1 commit
  26. 22 Feb, 2012 1 commit
    • Andrei Paskevich's avatar
      make api of maps/sets more consistent · 33bb423f
      Andrei Paskevich authored
      - change takes function as the first argument
      - add_new takes exception as the first argument
      - find_default is renamed to find_def and takes the default value
        as the first argument
      - find_option is renamed to find_opt (to align with find_exn and find_def)
      - default_option is renamed def_option
      33bb423f
  27. 21 Feb, 2012 1 commit
  28. 14 Feb, 2012 2 commits
  29. 13 Feb, 2012 1 commit