Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Ambrus Kaposi <kaposi...@gmail.com>
To: atm...@gmail.com
Cc: HomotopyT...@googlegroups.com
Subject: Re: [HoTT] Re: Where is the problem with initiality?
Date: Sat, 2 Jun 2018 07:21:06 +0200	[thread overview]
Message-ID: <CACSS4j=rgE5UduE5DMDw3YB5fGXmoW-FJRjyndZSLGpPpYxfBw@mail.gmail.com> (raw)
In-Reply-To: <864df164-59e9-4609-8e81-7c334be11e98@googlegroups.com>

On Fri, Jun 1, 2018 at 11:27 PM Matt Oliveri <atm...@gmail.com> wrote:
>
> On Friday, June 1, 2018 at 1:45:42 PM UTC-4, Eric Finster wrote:
>>
>> So from an internal perspective, I cannot think of any reason to
>> insist on decidability.
>
> I agree with this. And in particular, I think QIITs can define intrinsic syntax of (fully-annotated) extensional type theroy just fine. Equality reflection would be an extra equality constructor. Isn't that right? What do Thorsten and team think of that? Is it an infelicity of QIITs, perhaps because they're hSet truncated? Or is there a problem with ETT that structuralism doesn't shed light on? Or is ETT maybe not so bad?

Yes, the syntax for extensional type theory can be defined as a QIIT.

For me, the problem with it is that there is no easy way to input
terms in the computer: starting with a string, lexing, parsing it and
getting an untyped term, then typechecking the untyped term. During
bidirectional typechecking, we need that types in the QIIT have
decidable equality. See e.g.
https://bitbucket.org/akaposi/tt-in-tt/src/HEAD/Typecheck.agda
Equality of types is not decidable in ETT, even if we can normalise
terms (use it for programming).

But maybe there are other ways to build terms in this QIIT in a
convenient way (the NuPRL, Andromeda people know this), and then I
also don't see why we would insist on decidability of equality.

  reply	other threads:[~2018-06-02  5:21 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-22  5:46 Michael Shulman
2018-05-22 16:47 ` Ambrus Kaposi
2018-05-23 16:26 ` [HoTT] " Thorsten Altenkirch
2018-05-24  5:52   ` Michael Shulman
2018-05-24  8:11     ` Thorsten Altenkirch
2018-05-24  9:53       ` Ambrus Kaposi
2018-05-24 17:26         ` Michael Shulman
2018-05-26  9:21           ` Thomas Streicher
2018-05-26 11:47             ` Michael Shulman
2018-05-26 16:47               ` stre...
2018-05-27  5:14                 ` Bas Spitters
2018-05-28 22:39 ` Michael Shulman
2018-05-29  9:15   ` [HoTT] " Thorsten Altenkirch
2018-05-29 15:15     ` Michael Shulman
2018-05-30  9:33       ` Thomas Streicher
2018-05-30  9:37         ` Thorsten Altenkirch
2018-05-30 10:10           ` Thomas Streicher
2018-05-30 12:08             ` Thorsten Altenkirch
2018-05-30 13:40               ` Thomas Streicher
2018-05-30 14:38                 ` Thorsten Altenkirch
2018-05-30 10:53           ` Alexander Kurz
2018-05-30 12:05             ` Thorsten Altenkirch
2018-05-30 19:07               ` Michael Shulman
2018-05-31 10:06                 ` Thorsten Altenkirch
2018-05-31 11:05                   ` Michael Shulman
2018-05-31 19:02                     ` Alexander Kurz
2018-06-01  9:55                       ` Martin Escardo
2018-06-01 17:07                       ` Martín Hötzel Escardó
2018-06-01 17:43                         ` Eric Finster
2018-06-01 19:55                           ` Martín Hötzel Escardó
2018-06-01 20:59                             ` András Kovács
2018-06-01 21:06                               ` Martín Hötzel Escardó
2018-06-01 21:23                                 ` Michael Shulman
2018-06-01 21:53                                   ` Eric Finster
2018-06-01 22:09                                     ` Michael Shulman
2018-06-02 15:06                                       ` Eric Finster
2018-06-05 20:04                                         ` Michael Shulman
2018-06-02  5:13                                 ` Thomas Streicher
2018-06-01 21:52                               ` Jasper Hugunin
2018-06-01 22:00                                 ` Eric Finster
2018-06-01 21:27                           ` Matt Oliveri
2018-06-02  5:21                             ` Ambrus Kaposi [this message]
2018-06-02  6:01                               ` Thomas Streicher
2018-06-02 14:35                           ` Thorsten Altenkirch
2018-05-30 13:30             ` Jon Sterling
2018-06-05  7:52             ` Andrej Bauer
2018-06-05  8:37               ` David Roberts
2018-06-05  9:46                 ` Gabriel Scherer
2018-06-05 22:19                 ` Martín Hötzel Escardó
2018-06-05 22:54                   ` Martín Hötzel Escardó
2018-06-05 22:12               ` Richard Williamson
2018-06-06 15:05                 ` Thorsten Altenkirch
2018-06-06 19:25                   ` Richard Williamson
2018-05-29 14:00   ` Jon Sterling
2018-05-30 22:35     ` Michael Shulman
2018-05-31 10:48       ` Martín Hötzel Escardó
2018-05-31 11:09         ` Michael Shulman

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='CACSS4j=rgE5UduE5DMDw3YB5fGXmoW-FJRjyndZSLGpPpYxfBw@mail.gmail.com' \
    --to="kaposi..."@gmail.com \
    --cc="HomotopyT..."@googlegroups.com \
    --cc="atm..."@gmail.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).