1. 22 Sep, 2012 3 commits
  2. 11 Sep, 2012 1 commit
  3. 31 Aug, 2012 1 commit
  4. 24 Aug, 2012 1 commit
  5. 23 Aug, 2012 1 commit
  6. 05 Aug, 2012 1 commit
  7. 04 Aug, 2012 1 commit
  8. 03 Aug, 2012 1 commit
  9. 31 Jul, 2012 1 commit
  10. 28 Jul, 2012 4 commits
  11. 23 Jul, 2012 1 commit
  12. 20 Jul, 2012 4 commits
  13. 19 Jul, 2012 1 commit
  14. 16 Jul, 2012 2 commits
  15. 14 Jul, 2012 4 commits
  16. 12 Jul, 2012 2 commits
  17. 11 Jul, 2012 1 commit
  18. 08 Jul, 2012 3 commits
  19. 07 Jul, 2012 2 commits
  20. 06 Jul, 2012 1 commit
  21. 05 Jul, 2012 1 commit
  22. 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
  23. 27 Jun, 2012 1 commit