1. 12 May, 2017 3 commits
  2. 09 May, 2017 1 commit
  3. 13 Apr, 2017 1 commit
  4. 28 Mar, 2017 1 commit
  5. 23 Mar, 2017 1 commit
  6. 21 Mar, 2017 1 commit
  7. 16 Mar, 2017 5 commits
  8. 15 Mar, 2017 2 commits
  9. 14 Mar, 2017 1 commit
    • Robbert Krebbers's avatar
      Extend specialization patterns. · 87a8a19c
      Robbert Krebbers authored
      - Support for a `//` modifier to close the goal using `done`.
      - Support for framing in the `[#]` specialization pattern for
        persistent premises, i.e. `[# $H1 $H2]`
      - Add new "auto framing patterns" `[$]`, `[# $]` and `>[$]` that
        will try to solve the premise by framing. Hypothesis that are
        not framed are carried over to the next goal.
      87a8a19c
  10. 24 Feb, 2017 1 commit
  11. 22 Feb, 2017 1 commit
  12. 21 Feb, 2017 1 commit
  13. 15 Feb, 2017 2 commits
  14. 13 Feb, 2017 1 commit
  15. 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
  16. 11 Feb, 2017 3 commits
  17. 09 Feb, 2017 2 commits
  18. 06 Feb, 2017 1 commit
  19. 30 Jan, 2017 3 commits
    • Robbert Krebbers's avatar
      Support introduction patterns /=, {H}, {$H} in iDestruct. · 686f5740
      Robbert Krebbers authored
      This fixes issue #57.
      
      I considered supporting these introduction patterns also in a nested fashion --
      for example allowing `iDestruct foo as [H1 [{H1} H1 /= H2|H2]` -- but that
      turned out to be quite difficult.
      
      Where should we allow `/=`, `{H}` and `{$H}` exactly. Clearly something like
      `>/=` makes no sense, unless we adopt to some kind of 'stack like' semantics
      for introduction patterns as in ssreflect. Alternatively, we could only allow
      these patterns in the branches of the destructing introduction pattern
      `[... | ... | ...]` but that brings other complications, e.g.:
      
      - What to do with `(H1 & /= & H3)`?
      - How to distinguish the introduction patterns `[H _]` and `[_ H]` for
        destructing a spatial conjunction? We cannot simply match on the shape of the
        introduction pattern anymore, because one could also write `[_ H /=]`.
      686f5740
    • Robbert Krebbers's avatar
      6fc0ecff
    • Robbert Krebbers's avatar
      1805a435
  20. 29 Jan, 2017 1 commit
  21. 24 Jan, 2017 4 commits
  22. 23 Jan, 2017 2 commits
  23. 22 Jan, 2017 1 commit