Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: Michael Shulman <shu...@sandiego.edu>
To: Andrew Polonsky <andrew....@gmail.com>
Cc: Dan Licata <d...@cs.cmu.edu>,
	 Homotopy Type Theory <HomotopyT...@googlegroups.com>
Subject: Re: [HoTT] A puzzle about "univalent equality"
Date: Tue, 6 Sep 2016 05:32:19 -0700	[thread overview]
Message-ID: <CAOvivQwgfVzH9N_JhgdjB4KC5+LmMEjAJpO-mKo_Mm70OOgr4w@mail.gmail.com> (raw)
In-Reply-To: <CABcT7WBZo8bt6dtfDowd2nOYrtLPwsCC4Yxara1sZ5_oHeUQFw@mail.gmail.com>

Although, as Voevodsky showed, weak funext implies strong funext.

On Tue, Sep 6, 2016 at 12:30 AM, Andrew Polonsky
<andrew....@gmail.com> wrote:
> Thanks, Mike and Dan.  And congratulations on giving essentially
> identical solutions at essentially identical times, in two different
> languages!
>
>> I would be very surprised if there was something like this that was not provable in "book HoTT”.
>
> I believe there can't be, either.  But maybe this "belief" is really a
> matter of definition, in that the equalities which are "supposed to"
> hold, are precisely those which can be derived in book HoTT.
>
> What I find subtle in the above example is that it apparently cannot
> be done with the "pre-HoTT" FunExt axiom; you need to use the stronger
> formulation, that the canonical map (f=g -> f==g) is an equivalence,
> to make the transports compute.
>
> Cheers,
> Andrew
>
> --
> 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 HomotopyTypeThe...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

  reply	other threads:[~2016-09-06 12:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-05 16:54 Andrew Polonsky
2016-09-05 21:40 ` [HoTT] " Michael Shulman
2016-09-05 21:51 ` Dan Licata
2016-09-06  7:30   ` Andrew Polonsky
2016-09-06 12:32     ` Michael Shulman [this message]
2016-09-06 12:56       ` Dan Licata
2016-09-06 12:57       ` Peter LeFanu Lumsdaine
2016-09-06 13:44         ` Andrew Polonsky
2016-09-06 22:14           ` Martin Escardo
2016-09-07 23:18             ` Matt Oliveri
2016-09-08  4:14               ` Michael Shulman
2016-09-08  6:06                 ` Jason Gross
2016-09-08  9:11                   ` Martin Escardo
2016-09-08  6:34                 ` Matt Oliveri
2016-09-08  6:45                   ` Michael Shulman
2016-09-08  9:07                     ` Martin Escardo
2016-09-08  9:51                       ` Thomas Streicher
2016-09-19 12:40 ` Robin Adams

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=CAOvivQwgfVzH9N_JhgdjB4KC5+LmMEjAJpO-mKo_Mm70OOgr4w@mail.gmail.com \
    --to="shu..."@sandiego.edu \
    --cc="HomotopyT..."@googlegroups.com \
    --cc="andrew...."@gmail.com \
    --cc="d..."@cs.cmu.edu \
    /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).