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 04:17:51 -0800 (PST)	[thread overview]
Message-ID: <3d0f6986-0136-480f-8c01-b593cbe3fff9@googlegroups.com> (raw)
In-Reply-To: <CAOvivQzg9GEZV3bATTMUneRpC0J_V--Fdx3dio4-=A3zRnoOLA@mail.gmail.com>


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

On Saturday, February 9, 2019 at 3:34:22 PM UTC-5, Michael Shulman wrote:
>
> From an implementation point of view, I agree that in the long run we 
> should have proof assistants that don't hardcode a fixed set of 
> judgmental equalities.  But I don't think that means eliminating all 
> judgmental equalities; it just means making the logical framework more 
> flexible, such as Agda's ability to postulate new reductions or 
> Andromeda's framework with equality reflection.  In particular, the 
> new equalities that we postulate should still be *substitutive* (as 
> Jon says, allowing to perturb a judgment without altering the proof 
> object) rather than *transportive* (requiring the proof object to be 
> altered) -- I think Vladimir was the one who suggested words like 
> those.


I first heard those terms was on this list:
https://groups.google.com/forum/#!topic/homotopytypetheory/1bUtH8CLGQg

It seems from that discussion that they were associated with Vladimir 
Voevodsky's proposal for HTS. As a form of extensional type theory without 
any "built-in" implementation proposal, it seems like HTS has no notion of 
"proof object" in Jon's sense, which seems to be formal, checkable proofs. 
It's not that you couldn't come up with one, it just isn't specified. So I 
don't think HTS has any "definitional equality", in Jon's sense. But it 
seems like HTS' exact equality was considered substitutive nonetheless. In 
fact, it seems to me like what Vladimir meant by "substitutional" was that 
it doesn't cause coercions. Either because it's definitional, or because 
it's subsumptive (my term, from another message in this thread).

So I think you're misusing those terms.

Judgmental, definitional, substitutive, and computational equalities 
> are not exactly the same thing.  But the fact that there are so many 
> different but related points of view on similar and overlapping 
> concepts, and so many different but related uses and applications for 
> them, suggests to me that there is an important underlying 
> mathematical concept that should not lightly be discarded.
>

This is too vague. I wouldn't know whether I'm discarding it or not. You 
seem to be downplaying the differences between these notions. Why? If you 
don't care about the difference, why don't you just deal with strict or 
exact equality, and leave the implementation details to someone else? 
Coherence issues don't penetrate to a lower level than strict equality. 
Judgmental, definitional, and substitutive equality are special cases of 
strict equality that differ in their implementation properties.

-- 
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: 3541 bytes --]

  reply	other threads:[~2019-02-11 12:17 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 [this message]
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
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=3d0f6986-0136-480f-8c01-b593cbe3fff9@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).