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. 24 Apr, 2013 1 commit
  2. 22 Apr, 2013 1 commit
  3. 18 Apr, 2013 1 commit
  4. 16 Apr, 2013 1 commit
  5. 06 Mar, 2013 1 commit
  6. 03 Mar, 2013 1 commit
    • Andrei Paskevich's avatar
      track dangerous applications of equality · bb6734a1
      Andrei Paskevich authored
      In programs, but also in pure theories, it is not safe to compare
      arbitrary types. For example, if we have a record with ghost fields,
      a comparison may produce different results before and after ghost
      code elimination. Even for pure types like 'map' or 'set', it is
      unlikely that the result of logical equality will be the same as
      the result of OCaml structural equality on the implemented type.
      This commit makes the first step towards fixing this issue.
      We proceed in the following way:
      1. Every lsymbol (pure function or predicate symbol) carries
         a subset of type variables of its signature, called "opaque
         type variables". By marking a type variable 'a opaque in an
         lsymbol's signature, the user guarantees that this lsymbol
         can be implemented without ever comparing values of type 'a.
         In other words, this is a promise not to break into a type
         The corresponding syntax is: "predicate safe (x y : ~'a)".
         All type variables in undefined symbols are non-opaque,
         unless annotated otherwise. Non-opaque is the default
         to keep the change conservative.
         Opacity of type variables in defined symbols is inferred
         from the definition. If the definition violates a given
         opacity annotation, an exception is raised. Notice that
         we only check definitions in _theory_ declarations. One
         can define an lsymbol in a _task_ in a way that violates
         opacity. We cannot forbid it, because various elimination
         transformations would replace safe operations (such as
         matching) with equalities. This is not a problem, since in
         the pure logical realm of provers opacity is not required
         One exception would be Coq, whose transformation chain must
         never perform such operations.
         All type variables in inductive predicates are non-opaque.
         Indeed, we can redefine equality via an inductive predicate.
         [TODO: find safe forms of inductive definitions and implement
         more reasonable restrictions.]
         All type variables in constructors and field symbols are opaque.
         It is forbidden to instantiate an opacity-preserving symbol
         with an opacity-breaking one in a clone substitution.
      2. Similar type variable tracking is implemented for program symbols.
         Type variables in the signature of a "val" are non-opaque unless
         annotated otherwise. Opacity of type variables in defined symbols
         is inferred from the definition, and an exception is raised, if
         a given annotation is violated.
         The internal mechanism of tracking is different: the "eff_compar"
         field in effects contains the type variables that occur under
         equality or any other opacity-breaking operation. In this respect,
         our API is inconsistent between lsymbols and psymbols: the former
         asks for the opaque tvsymbols, the latter requires us to fill the
         spec with "comparison effects" for the non-opaque ones. [TODO:
         add the "~opaque" argument to create_psymbol and make the WhyML
         core fill the effect under the hood.]
         Every time an lsymbol or a psymbol is applied in a program,
         we check the substitution into its signature's type variables.
         If a non-opaque type variable is instantiated with a program type,
         an exception is raised. [TODO: be more precise and reject only
         types with ghost and model components - being mutable, private,
         or carrying an invariant doesn't conflict with equality.]
         Notice that we do not allow to compare program types even in
         the ghost code. This is not needed if we only consider the
         problems of the code extraction, but _might_ be necessary,
         if we also want to protect Coq realisations (see below).
      This commit fixes the immediate problem of breaking the ghost
      guarantees when equality or some other opacity-breaking lsymbol
      is applied in a program to a type with ghost or "model" parts.
      This leaves the problem of code extraction for programs that
      compare complex types such as maps or sets (Coq driver is
      affected by this, too, I guess). The next step is to provide
      annotations for problematic type constructors. A declaration
      "type ~map 'a 'b" would mean "logical equality on this type
      is likely to be different from the structural equality on any
      implementation of this type - therefore do not apply equality
      to it: neither in programs (because this can't be implemented),
      nor in pure functions (because they are extracted, too, and
      because this can't be realized with Leibniz equality in Coq)."
      [TODO: discuss and implement.]
      [TODO: mb choose better term for "opaque" and notation for ~'a.]
  7. 09 Feb, 2013 1 commit
    • Andrei Paskevich's avatar
      whyml: accept infix relation chains · 919d60bf
      Andrei Paskevich authored
      In a chain "e1 op1 e2 op2 e3 op3 e4", each relation symbol is either:
      - an infix symbol "=" or "<>", or
      - a binary symbol whose value type is Bool.bool or Prop (for lsymbols)
        and whose arguments' types are not Bool.bool.
      In other words, we interpret a chain as a conjunction only if there
      is no possibility(*) to interpret it as a superposition. The exception
      is only made for "=" and "<>", which are _always_ considered as
      chainable, even if they are redefined with some bogus type signatures.
      Notice that redefining "<>" has no effect whatsoever, since "<>" is
      always treated as negated "=".
      As for the evaluation order, the chain above would be equivalent to:
          let x2 = e2 in
          (e1 op1 x2) &&
              let x3 = e3 in
              (x2 op2 x3) &&
                  (x3 op3 e4)
      This is due to the fact that lazy conjunctions are evaluated from
      left to right, function arguments are evaluated from right to left,
      and no expression should be evaluated twice.
      [*] well, not really, since...
  8. 05 Jan, 2013 1 commit
  9. 13 Nov, 2012 1 commit
  10. 20 Oct, 2012 1 commit
    • Andrei Paskevich's avatar
      simplify copyright headers · 11598d2b
      Andrei Paskevich authored
      + create AUTHORS file
      + fix the linking exception in LICENSE
      + update the "About" in IDE
      + remove the trailing whitespace
      + inflate my scores at Ohloh
  11. 17 Oct, 2012 1 commit
    • Andrei Paskevich's avatar
      move whyml to the Why3 library · 4599fe6b
      Andrei Paskevich authored
      + do not build src/programs/
      + build the library in lib/why3/
      + fix use_api.ml for the case when Alt-Ergo is not present
      + distribute lib/coq/BuiltIn.v
      + rename src/config to src/why3config
      + rename src/bench to src/why3bench
      + move src/config.ml to src/util/
  12. 20 Jul, 2012 1 commit
  13. 12 Jul, 2012 1 commit
  14. 05 Jul, 2012 1 commit
  15. 23 Jun, 2012 1 commit
  16. 17 Jun, 2012 2 commits
  17. 16 Jun, 2012 1 commit
  18. 06 Jun, 2012 1 commit
  19. 05 Jun, 2012 1 commit
  20. 25 May, 2012 1 commit
  21. 22 May, 2012 1 commit
  22. 15 May, 2012 2 commits
  23. 14 May, 2012 1 commit
  24. 10 May, 2012 1 commit
  25. 17 Apr, 2012 1 commit
  26. 16 Apr, 2012 1 commit
  27. 09 Apr, 2012 1 commit
  28. 01 Jul, 2011 1 commit
  29. 24 May, 2011 1 commit
  30. 13 Dec, 2010 1 commit
  31. 08 Jul, 2010 1 commit
    • Andrei Paskevich's avatar
      Reworking tags and transformations, stage 3: · dd3aac24
      Andrei Paskevich authored
      - everything is converted to the new shiny way of doing things.
        Well, everything except Gappa, which seems very unifinished anyway,
        and Encoding_instantiate, which is too complex and would like to 
        update it with François.
      Also, I commented a little piece of exception reporting in manager/,
      will see it with Claude.
      Please inform me about any bugs, ugly APIs, and proposed corrections.
      All the non-implemented things, mentioned in the previous commit
      message are still in the TODO list and will be done soon.
  32. 19 Mar, 2010 1 commit
    • Francois Bobot's avatar
      · 23ca2d16
      Francois Bobot authored
         - Util : Ajout de Creation generique de Set,Map et Hashtbl 
                  quand on a un tag et une egalitée physique
         - Hashweak : Implementation de l'idee de Jean-Christophe et Andreï
         - Register : Simplification des types comme demandé par Jean-Christophe
                      Mise à jour des fichiers qui en dépendait
         - Theory   : Ajout d'une facilité de création des th_inst
         - Encoding_decorate : Prelude pour l'encodage de Stéphane en utilisant flat_theory d'Andreï
         - Ty : Ajout de Sty, Mty et Hty
         - Main : Reduction de la taille des lignes à 80 colonnes
  33. 18 Mar, 2010 1 commit
  34. 17 Mar, 2010 2 commits
  35. 12 Mar, 2010 1 commit
  36. 10 Mar, 2010 2 commits