Skip to content
Snippets Groups Projects
  1. Mar 05, 2017
  2. Feb 24, 2017
  3. Feb 22, 2017
  4. Feb 21, 2017
  5. Feb 15, 2017
  6. Feb 13, 2017
  7. Feb 12, 2017
    • 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
  8. Feb 11, 2017
  9. Feb 09, 2017
  10. Feb 06, 2017
  11. Jan 30, 2017
    • 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
  12. Jan 29, 2017
  13. Jan 24, 2017
  14. Jan 23, 2017
  15. Jan 22, 2017
  16. Jan 20, 2017
  17. Jan 12, 2017
  18. Jan 11, 2017
  19. Jan 05, 2017
  20. Jan 04, 2017
  21. Jan 03, 2017
  22. Jan 01, 2017
  23. Dec 28, 2016
  24. Dec 27, 2016
Loading