1. 28 Aug, 2017 5 commits
  2. 24 Aug, 2017 2 commits
  3. 22 Aug, 2017 1 commit
  4. 20 Aug, 2017 1 commit
  5. 04 Aug, 2017 1 commit
  6. 12 Jul, 2017 1 commit
  7. 12 Jun, 2017 1 commit
  8. 08 Jun, 2017 2 commits
  9. 12 May, 2017 4 commits
  10. 09 May, 2017 1 commit
  11. 27 Apr, 2017 2 commits
  12. 26 Apr, 2017 1 commit
    • Robbert Krebbers's avatar
      Fix bug #85 in another way. · 293fb6c7
      Robbert Krebbers authored
      After discussing this with Ralf, again, it turned out that using a bar
      instead of a turnstyle would be better. When formalizing type systems, one
      often wants to use a turnstyle in other notations (the typing judgment),
      so having the turnstyle in the proofmode notation is confusing.
      293fb6c7
  13. 13 Apr, 2017 2 commits
  14. 07 Apr, 2017 1 commit
  15. 30 Mar, 2017 1 commit
  16. 28 Mar, 2017 2 commits
  17. 24 Mar, 2017 4 commits
    • Robbert Krebbers's avatar
      Make big_opL type class opaque. · 02a0929d
      Robbert Krebbers authored
      This commit fixes the issues that refolding of big operators did not work nicely
      in the proof mode, e.g., given:
      
          Goal forall M (P : nat → uPred M) l,
            ([∗ list] x ∈ 10 :: l, P x) -∗ True.
          Proof. iIntros (M P l) "[H1 H2]".
      
      We got:
      
          "H1" : P 10
          "H2" : (fix
                  big_opL (M0 : ofeT) (o : M0 → M0 → M0) (H : Monoid o) (A : Type)
                          (f : nat → A → M0) (xs : list A) {struct xs} : M0 :=
                    match xs with
                    | [] => monoid_unit
                    | x :: xs0 => o (f 0 x) (big_opL M0 o H A (λ n : nat, f (S n)) xs0)
                    end) (uPredC M) uPred_sep uPred.uPred_sep_monoid nat
                   (λ _ x : nat, P x) l
          --------------------------------------∗
          True
      
      The problem here is that proof mode looked for an instance of `IntoAnd` for
      `[∗ list] x ∈ 10 :: l, P x` and then applies the instance for separating conjunction
      without folding back the fixpoint. This problem is not specific to the Iris proof
      mode, but more of a general problem of Coq's `apply`, for example:
      
          Goal forall x l, Forall (fun _ => True) (map S (x :: l)).
          Proof.
            intros x l. constructor.
      
      Gives:
      
           Forall (λ _ : nat, True)
             ((fix map (l0 : list nat) : list nat :=
                match l0 with
                | [] => []
                | a :: t => S a :: map t
                end) l)
      
      This commit fixes this issue by making the big operators type class opaque and instead
      handle them solely via corresponding type classes instances for the proof mode tactics.
      
      Furthermore, note that we already had instances for persistence and timelessness. Those
      were really needed; computation did not help to establish persistence when the list in
      question was not a ground term. In fact, the sitation was worse, to establish persistence
      of `[∗ list] x ∈ 10 :: l, P x` it could either use the persistence instance of big ops
      directly, or use the persistency instance for `∗` first. Worst case, this can lead to an
      exponential blow up because of back tracking.
      02a0929d
    • Robbert Krebbers's avatar
    • Robbert Krebbers's avatar
      Remove Hints and Instances that are no longer needed. · c52ff261
      Robbert Krebbers authored
      Big ops over list with a cons reduce, hence these just follow
      immediately from conversion.
      c52ff261
    • Robbert Krebbers's avatar
      15bfdc15
  18. 23 Mar, 2017 1 commit
  19. 21 Mar, 2017 4 commits
  20. 20 Mar, 2017 1 commit
  21. 16 Mar, 2017 2 commits