1. 21 Jun, 2018 1 commit
  2. 17 Jun, 2018 2 commits
  3. 14 Jun, 2018 1 commit
  4. 08 Jun, 2018 1 commit
  5. 07 Jun, 2018 1 commit
    • Andrei Paskevich's avatar
      WhyML: allow return types with names: f (a:int) : (x: int, ghost y: int) · 0ffeb3d4
      Andrei Paskevich authored
      These names are only visible under "ensures" but not under "returns".
      If the result is named, the special variable "result" is not used.
      In a tuple, either each component should be named, or none at all.
      Underscores are allowed. Parentheses around the return type are required.
      Each name must be given its own type: "f () : (x y: int)" is rejected.
      Identifiers without cast are treated as types, not as names.
      To name the result without giving its type, use "returns".
      0ffeb3d4
  6. 05 Jun, 2018 2 commits
  7. 01 Jun, 2018 1 commit
  8. 31 May, 2018 4 commits
  9. 25 May, 2018 2 commits
  10. 17 May, 2018 1 commit
  11. 15 May, 2018 1 commit
  12. 09 May, 2018 1 commit
  13. 01 May, 2018 3 commits
  14. 30 Apr, 2018 1 commit
  15. 16 Apr, 2018 2 commits
  16. 13 Apr, 2018 1 commit
  17. 11 Apr, 2018 2 commits
  18. 10 Apr, 2018 1 commit
  19. 04 Apr, 2018 2 commits
  20. 30 Mar, 2018 3 commits
  21. 29 Mar, 2018 4 commits
  22. 28 Mar, 2018 1 commit
  23. 27 Mar, 2018 1 commit
  24. 26 Mar, 2018 1 commit