1. 28 Oct, 2017 1 commit
  2. 27 Oct, 2017 1 commit
  3. 25 Oct, 2017 3 commits
  4. 05 Oct, 2017 1 commit
  5. 28 Sep, 2017 1 commit
  6. 27 Sep, 2017 3 commits
  7. 21 Sep, 2017 1 commit
  8. 28 Aug, 2017 2 commits
  9. 24 Aug, 2017 1 commit
  10. 17 May, 2017 1 commit
  11. 13 Apr, 2017 2 commits
  12. 11 Apr, 2017 1 commit
  13. 21 Mar, 2017 1 commit
  14. 15 Mar, 2017 1 commit
  15. 14 Mar, 2017 2 commits
  16. 12 Mar, 2017 1 commit
  17. 11 Mar, 2017 1 commit
  18. 10 Mar, 2017 1 commit
  19. 21 Feb, 2017 1 commit
  20. 15 Feb, 2017 1 commit
  21. 13 Feb, 2017 3 commits
  22. 12 Feb, 2017 1 commit
    • Robbert Krebbers's avatar
      Make iSpecialize work with coercions. · f1b30a2e
      Robbert Krebbers authored
      For example, when having `"H" : ∀ x : Z, P x`, using
      `iSpecialize ("H" $! (0:nat))` now works. We do this by first
      resolving the `IntoForall` type class, and then instantiating
      the quantifier.
      f1b30a2e
  23. 23 Jan, 2017 1 commit
  24. 22 Jan, 2017 1 commit
  25. 05 Jan, 2017 1 commit
  26. 03 Jan, 2017 1 commit
  27. 28 Dec, 2016 1 commit
  28. 09 Dec, 2016 2 commits
  29. 24 Nov, 2016 1 commit
  30. 22 Nov, 2016 1 commit
    • Robbert Krebbers's avatar
      Make nclose an explicit coercion. · 274209c2
      Robbert Krebbers authored and Ralf Jung's avatar Ralf Jung committed
      We do this by introducing a type class UpClose with notation ↑.
      
      The reason for this change is as follows: since `nclose : namespace
      → coPset` is declared as a coercion, the notation `nclose N ⊆ E` was
      pretty printed as `N ⊆ E`. However, `N ⊆ E` could not be typechecked
      because type checking goes from left to right, and as such would look
      for an instance `SubsetEq namespace`, which causes the right hand side
      to be ill-typed.
      274209c2