1. 27 Jul, 2016 1 commit
    • Robbert Krebbers's avatar
      Make type class inference for inG less eager. · a0348d7c
      Robbert Krebbers authored
      This way, it won't pick arbitrary (and possibly wrong!) inG instances
      when multiple ones are available. We achieve this by declaring:
      
        Hint Mode inG - - +
      
      So that type class inference only succeeds when the type of the ghost
      variable does not include any evars.
      
      This required me to make some minor changes throughout the whole
      development making some types explicit.
      a0348d7c
  2. 20 Jul, 2016 3 commits
  3. 19 Jul, 2016 6 commits
  4. 18 Jul, 2016 1 commit
  5. 15 Jul, 2016 2 commits
  6. 13 Jul, 2016 1 commit
  7. 11 Jul, 2016 1 commit
  8. 03 Jul, 2016 1 commit
  9. 30 Jun, 2016 1 commit
  10. 23 Jun, 2016 2 commits
  11. 16 Jun, 2016 1 commit
  12. 14 Jun, 2016 1 commit
  13. 01 Jun, 2016 3 commits
  14. 31 May, 2016 2 commits
  15. 30 May, 2016 1 commit
  16. 24 May, 2016 5 commits
    • Robbert Krebbers's avatar
      Change notations of big_ops for upred. · 93792f5c
      Robbert Krebbers authored
      Rationale: to make the code closer to what is on paper, I want the notations
      to look like quantifiers, i.e. have a binder built-in. I thus introduced the
      following notations:
      
        [★ map] k ↦ x ∈ m, P
        [★ set] x ∈ X, P
      
      The good thing - contrary to the notations that we had before that required an
      explicit lambda - is that type annotations of k and x are now not printed
      making goals much easier to read.
      93792f5c
    • Robbert Krebbers's avatar
    • Robbert Krebbers's avatar
      Merge iAssert and iPvsAssert. · e965b669
      Robbert Krebbers authored
      To do so, we have introduced the specialization patterns:
      
        =>[H1 .. Hn] and =>[-H1 .. Hn]
      
      That generate a goal in which the view shift is preserved. These specialization
      patterns can also be used for e.g. iApply.
      
      Note that this machinery is not tied to primitive view shifts, and works for
      various kinds of goal (as captured by the ToAssert type class, which describes
      how to transform the asserted goal based on the main goal).
      
      TODO: change the name of these specialization patterns to reflect this
      generality.
      e965b669
    • Robbert Krebbers's avatar
      eacb1c46
    • Robbert Krebbers's avatar
      Make specialization patterns for persistent premises more uniform. · 65bfa071
      Robbert Krebbers authored
      Changes:
      - We no longer have a different syntax for specializing a term H : P -★ Q whose
        range P or domain Q is persistent. There is just one syntax, and the system
        automatically determines whether either P or Q is persistent.
      - While specializing a term, always modalities are automatically stripped. This
        gets rid of the specialization pattern !.
      - Make the syntax of specialization patterns more consistent. The syntax for
        generating a goal is [goal_spec] where goal_spec is one of the following:
      
          H1 .. Hn : generate a goal using hypotheses H1 .. Hn
         -H1 .. Hn : generate a goal using all hypotheses but H1 .. Hn
                 # : generate a goal for the premise in which all hypotheses can be
                     used. This is only allowed when specializing H : P -★ Q where
                     either P or Q is persistent.
                 % : generate a goal for a pure premise.
      65bfa071
  17. 10 May, 2016 2 commits
  18. 06 May, 2016 4 commits
  19. 02 May, 2016 1 commit
  20. 26 Apr, 2016 1 commit