Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Matt Oliveri <atmacen@gmail.com>
To: Homotopy Type Theory <HomotopyTypeTheory@googlegroups.com>
Subject: Re: [HoTT] Re: Why do we need judgmental equality?
Date: Mon, 11 Feb 2019 11:27:23 -0800 (PST)	[thread overview]
Message-ID: <7b35e7cb-3021-44cd-8c97-a7cc1159f999@googlegroups.com> (raw)
In-Reply-To: <CAOvivQwKBZorQccU1EwQw6WsOU+U7RA85EexGLUbWUWs_6xPQw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 3407 bytes --]

Jon's definitional equality is based on proof objects. The Andromeda terms 
aren't proof objects, since you can't check just a term. So the fact that 
Andromeda terms don't have coercions for strict equality doesn't do 
anything for definitional equality. I would guess AML programs should be 
considered the relevant proof objects. I'd say definitional equality in 
Andromeda is pretty interesting, since algebraic effect handlers let you 
locally add new automation for equality. But it can't be as rich as strict 
equality (if you have e.g. induction on nats). And globally, it sounds like 
it's just alpha conversion.

On Monday, February 11, 2019 at 12:20:46 PM UTC-5, Michael Shulman wrote:
>
> FWIW, I think the only thing I have against NuPRL "in principle" is 
> that it seems to be closely tied to one particular model, which is the 
> opposite of what I want my type theories to achieve.  I say "seems" 
> because then someone says something like Jon's "Nuprl's underlying 
> objects are untyped -- but that is not an essential part of the idea", 
> providing an instance of the problem I have with NuPRL "in practice", 
> which is that every time I think I understand it someone proves me 
> wrong.  (-:O 
>
> Can you explain the difference between "definitional" (whatever that 
> means) and "strict" equality in Andromeda?  Of course there is the 
> technical difference between judgmental equality and the equality 
> type, but that doesn't seem to me to be a "real" difference in the 
> presence of equality reflection, particularly at the purely 
> philosophical level at which a phrase like "equality of sense" has to 
> be interpreted.  As far as I know, even beta-reduction has no 
> privileged status in the Andromeda core -- although I suppose 
> alpha-conversion probably does. 
>
>
> On Mon, Feb 11, 2019 at 7:09 AM Matt Oliveri <atm...@gmail.com 
> <javascript:>> wrote: 
> > 
> > It looks like Jon is with you regarding definitional/substitutive 
> equality, since he considers Nuprl's subtitutive equality to be alpha 
> conversion. From the old discussion about it, I had figured Nuprl's 
> substitutive equality was the equality type. I guess I'll avoid that term. 
> > 
> > So I'll ask a more concrete question. You seem to be more open to 
> Andromeda than Nuprl. It has a difference between definitional equality (in 
> Jon's sense) and the (strict/exact) equality type for approximately the 
> same reason as Nuprl. If the theory you're using is HTS, then there's also 
> path types. So I gather path types are what you want to take as equality of 
> reference. Which is equality of sense? 
> > 
> > Regarding the paragraph I said was vague, my complaint really is that I 
> don't know what you're getting at. I recommended strict or exact equality 
> as possible (informal) interpretations. This doesn't mean there needs to be 
> something called "strict equality" in the system definition, for example, 
> it means you recognize a strict equality notion when you see one. I don't 
> know how to recognize the kind of equality you were getting at in that 
> paragraph. 
>

-- 
You received this message because you are subscribed to the Google Groups "Homotopy Type Theory" group.
To unsubscribe from this group and stop receiving emails from it, send an email to HomotopyTypeTheory+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 4135 bytes --]

  parent reply	other threads:[~2019-02-11 19:27 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30 11:54 [HoTT] " Felix Rech
2019-02-05 23:00 ` [HoTT] " Matt Oliveri
2019-02-06  4:13   ` Anders Mörtberg
2019-02-09 11:55     ` Felix Rech
2019-02-16 15:59     ` Thorsten Altenkirch
2019-02-17  1:25       ` Michael Shulman
2019-02-17  7:56         ` Thorsten Altenkirch
2019-02-17  9:14           ` Matt Oliveri
2019-02-17  9:18           ` Michael Shulman
2019-02-17 10:52             ` Thorsten Altenkirch
2019-02-17 11:35               ` streicher
2019-02-17 11:44                 ` Thorsten Altenkirch
2019-02-17 14:24                   ` Bas Spitters
2019-02-17 19:36                   ` Thomas Streicher
2019-02-17 21:41                     ` Thorsten Altenkirch
2019-02-17 12:08             ` Matt Oliveri
2019-02-17 12:13               ` Matt Oliveri
2019-02-20  0:22               ` Michael Shulman
2019-02-17 14:22           ` [Agda] " Andreas Abel
2019-02-17  9:05         ` Matt Oliveri
2019-02-17 13:29         ` Nicolai Kraus
2019-02-08 21:19 ` Martín Hötzel Escardó
2019-02-08 23:31   ` Valery Isaev
2019-02-09  1:41     ` Nicolai Kraus
2019-02-09  8:04       ` Valery Isaev
2019-02-09  1:58     ` Jon Sterling
2019-02-09  8:16       ` Valery Isaev
2019-02-09  1:30   ` Nicolai Kraus
2019-02-09 11:38   ` Thomas Streicher
2019-02-09 13:29     ` Thorsten Altenkirch
2019-02-09 13:40       ` Théo Winterhalter
2019-02-09 11:57   ` Felix Rech
2019-02-09 12:39     ` Martín Hötzel Escardó
2019-02-11  6:58     ` Matt Oliveri
2019-02-18 17:37   ` Martín Hötzel Escardó
2019-02-18 19:22     ` Licata, Dan
2019-02-18 20:23       ` Martín Hötzel Escardó
2019-02-09 11:53 ` Felix Rech
2019-02-09 14:04   ` Nicolai Kraus
2019-02-09 14:26     ` Gabriel Scherer
2019-02-09 14:44     ` Jon Sterling
2019-02-09 20:34       ` Michael Shulman
2019-02-11 12:17         ` Matt Oliveri
2019-02-11 13:04           ` Michael Shulman
2019-02-11 15:09             ` Matt Oliveri
2019-02-11 17:20               ` Michael Shulman
2019-02-11 18:17                 ` Thorsten Altenkirch
2019-02-11 18:45                   ` Alexander Kurz
2019-02-11 22:58                     ` Thorsten Altenkirch
2019-02-12  2:09                       ` Jacques Carette
2019-02-12 11:03                   ` Matt Oliveri
2019-02-12 15:36                     ` Thorsten Altenkirch
2019-02-12 15:59                       ` Matt Oliveri
2019-02-11 19:27                 ` Matt Oliveri [this message]
2019-02-11 21:49                   ` Michael Shulman
2019-02-12  9:01                     ` Matt Oliveri
2019-02-12 17:54                       ` Michael Shulman
2019-02-13  6:37                         ` Matt Oliveri
2019-02-13 10:01                           ` Ansten Mørch Klev
2019-02-11 20:11                 ` Matt Oliveri
2019-02-11  8:23       ` Matt Oliveri
2019-02-11 13:03         ` Jon Sterling
2019-02-11 13:22           ` Matt Oliveri
2019-02-11 13:37             ` Jon Sterling
2019-02-11  6:51   ` Matt Oliveri
2019-02-09 12:30 ` [HoTT] " Thorsten Altenkirch
2019-02-11  7:01   ` Matt Oliveri
2019-02-11  8:04     ` Valery Isaev
2019-02-11  8:28       ` Matt Oliveri
2019-02-11  8:37         ` Matt Oliveri
2019-02-11  9:32           ` Rafaël Bocquet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7b35e7cb-3021-44cd-8c97-a7cc1159f999@googlegroups.com \
    --to=atmacen@gmail.com \
    --cc=HomotopyTypeTheory@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).