Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Thomas Streicher <stre...@mathematik.tu-darmstadt.de>
To: Jon Sterling <j...@jonmsterling.com>
Cc: HomotopyT...@googlegroups.com
Subject: Re: [HoTT] Conjecture
Date: Thu, 6 Apr 2017 13:52:48 +0200	[thread overview]
Message-ID: <20170406115247.GC25210@mathematik.tu-darmstadt.de> (raw)
In-Reply-To: <1491438219.730556.935704416.05FD6770@webmail.messagingengine.com>

> This looks like a very interesting paper, thank you for sharing. I look
> forward to reading it in more detail.
> 
> I am curious, does this development use univalence except to establish
> functional extensionality and propositional extensionality? The reason I
> ask is, I wonder if it is possible to do a similar development of
> computability theory in extensional type theory and get analogous
> results. Additionally, I am curious whether you have found cases in
> which univalence clarifies or sharpens this development, since I'm
> trying to keep track of interesting use-cases of univalence.

For synthetic domain theory a formulation in extensional type theory
has been given in

MR1694130 (2000f:68069) 
Reus, Bernhard; Streicher, Thomas
General synthetic domain theory ¡X a logical approach. (English summary)
Math. Structures Comput. Sci. 9 (1999), no. 2, 177¡V223.

There is no need whatsoever to use univalence or something like that.
The only benefit would be to solve domain equations up to equality
which even computer scientists find unnecessary (for good reasons).

Andrej Bauer has written on Synthetic Recursion Theory, see
math.andrej.com/data/synthetic.pdf.

So I tend to the opinion that theer can't be an intrinsic use of
Univalence or HITs. But if there is I am curious to learn which one!

Thomas

  parent reply	other threads:[~2017-04-06 11:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 21:57 Conjecture Martin Escardo
2017-03-29 21:08 ` [HoTT] Conjecture Nicolai Kraus
2017-03-29 22:05   ` Martin Escardo
2017-03-30 10:59     ` Michael Shulman
2017-03-30 19:22       ` Egbert Rijke
2017-03-30 23:02         ` Nicolai Kraus
2017-03-30 22:49     ` Nicolai Kraus
2017-03-31 16:09       ` Martin Escardo
2017-04-05 19:37         ` Martin Escardo
2017-04-06  0:23           ` Jon Sterling
2017-04-06  5:55             ` Martin Escardo
2017-04-06 12:40               ` Vladimir Voevodsky
2017-04-06 13:50                 ` Martin Escardo
     [not found]                   ` <81c0782f-9287-4111-a4f1-01cb9c87c7e8@cs.bham.ac.uk>
2017-04-06 16:09                     ` Martin Escardo
2017-04-06 11:52             ` Thomas Streicher [this message]
2017-04-07  9:49               ` Martin Escardo
2017-04-07 17:11                 ` Michael Shulman
2017-04-07 18:10                   ` Martin Escardo
2017-04-03  0:35 ` Conjecture Daniel R. Grayson
2017-04-03  2:20   ` [HoTT] Conjecture Favonia
2017-04-03  9:56   ` Nicolai Kraus
2017-04-03 11:50     ` Daniel R. Grayson

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=20170406115247.GC25210@mathematik.tu-darmstadt.de \
    --to="stre..."@mathematik.tu-darmstadt.de \
    --cc="HomotopyT..."@googlegroups.com \
    --cc="j..."@jonmsterling.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).