From: Matt Oliveri <atm...@gmail.com>
To: Homotopy Type Theory <HomotopyT...@googlegroups.com>
Subject: Re: [HoTT] Impredicative set + function extensionality + proof irrelevance consistent?
Date: Mon, 18 Dec 2017 04:09:31 -0800 (PST) [thread overview]
Message-ID: <58e6faf9-7b23-44ae-a039-ef17f770cd2e@googlegroups.com> (raw)
In-Reply-To: <A88995F3-43D1-43A2-A448-3C6EFC422D8E@exmail.nottingham.ac.uk>
[-- Attachment #1.1: Type: text/plain, Size: 589 bytes --]
I don't understand these things you wrote:
On Monday, December 18, 2017 at 5:10:15 AM UTC-5, Thorsten Altenkirch wrote:
>
> Interestingly it seems that QITs are more expressive then quotients (which
> can be encoded impredicatively).
>
>
> And as I said above, QITs are an interesting extension which in some
> instances avoids appealing to the axiom of choice.
>
Like, in a constructive, predicative system without any choice principles,
and where quotients are not expressed as QITs, is there an expressiveness
difference? (I'm thinking of Computational Type Theory, for example.)
[-- Attachment #1.2: Type: text/html, Size: 875 bytes --]
next prev parent reply other threads:[~2017-12-18 12:09 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 4:22 Kristina Sojakova
2017-12-11 11:42 ` [HoTT] " Jon Sterling
2017-12-11 12:15 ` Kristina Sojakova
2017-12-11 12:43 ` Jon Sterling
2017-12-11 14:28 ` Thomas Streicher
2017-12-11 14:32 ` Kristina Sojakova
2017-12-11 14:23 ` Thorsten Altenkirch
2017-12-12 10:15 ` Andrea Vezzosi
2017-12-12 11:03 ` Thorsten Altenkirch
2017-12-12 12:02 ` Thomas Streicher
2017-12-12 12:21 ` Thorsten Altenkirch
2017-12-12 13:17 ` Jon Sterling
2017-12-12 19:29 ` Thomas Streicher
2017-12-12 19:52 ` Martin Escardo
2017-12-12 23:14 ` Michael Shulman
2017-12-14 12:32 ` Thorsten Altenkirch
2017-12-14 18:52 ` Michael Shulman
2017-12-16 15:21 ` Thorsten Altenkirch
2017-12-17 12:55 ` Michael Shulman
2017-12-17 17:08 ` Ben Sherman
2017-12-17 17:16 ` Thorsten Altenkirch
2017-12-17 22:43 ` Floris van Doorn
2017-12-15 17:00 ` Thomas Streicher
2017-12-17 8:47 ` Thorsten Altenkirch
2017-12-17 10:21 ` Thomas Streicher
2017-12-17 11:39 ` Thorsten Altenkirch
2017-12-18 7:41 ` Matt Oliveri
2017-12-18 10:00 ` Michael Shulman
2017-12-18 11:55 ` Matt Oliveri
2017-12-18 16:24 ` Michael Shulman
2017-12-18 20:08 ` Matt Oliveri
2017-12-18 10:10 ` Thorsten Altenkirch
2017-12-18 11:17 ` Matt Oliveri
2017-12-18 12:09 ` Matt Oliveri [this message]
2017-12-18 11:52 ` Thomas Streicher
2017-12-19 11:26 ` Thorsten Altenkirch
2017-12-19 13:52 ` Andrej Bauer
2017-12-19 14:44 ` Thorsten Altenkirch
2017-12-19 15:31 ` Thomas Streicher
2017-12-19 16:10 ` Thorsten Altenkirch
2017-12-19 16:31 ` Thomas Streicher
2017-12-19 16:37 ` Thorsten Altenkirch
2017-12-20 11:00 ` Thomas Streicher
2017-12-20 11:16 ` Thorsten Altenkirch
2017-12-20 11:41 ` Thomas Streicher
2017-12-21 0:42 ` Matt Oliveri
2017-12-22 11:18 ` Thorsten Altenkirch
2017-12-22 21:20 ` Martín Hötzel Escardó
2017-12-22 21:36 ` Martín Hötzel Escardó
2017-12-23 0:25 ` Matt Oliveri
2017-12-19 16:41 ` Steve Awodey
2017-12-20 0:14 ` Andrej Bauer
2017-12-20 3:55 ` Steve Awodey
[not found] ` <fa8c0c3c-4870-4c06-fd4d-70be992d3ac0@skyskimmer.net>
2017-12-14 13:28 ` Thorsten Altenkirch
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=58e6faf9-7b23-44ae-a039-ef17f770cd2e@googlegroups.com \
--to="atm..."@gmail.com \
--cc="HomotopyT..."@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).