Discussion of Homotopy Type Theory and Univalent Foundations
 help / color / mirror / Atom feed
From: xieyuheng <xyheme@gmail.com>
To: Homotopy Type Theory <HomotopyTypeTheory@googlegroups.com>
Subject: [HoTT] Re: is there a categorical construction to generalize arrow composition, by allowing domain and codomain to be refined (or changed) by the composition ?
Date: Tue, 19 Jun 2018 23:02:52 -0700 (PDT)	[thread overview]
Message-ID: <ef21d057-acd4-4e5d-9411-5beaa2dc3195@googlegroups.com> (raw)
In-Reply-To: <9b68a44e-7c9c-451b-8aab-a7a4c972ba6c@googlegroups.com>


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

Oh! I mistakenly thought a polymorphism is a morphism in a polycategory,
only later realized that polymorphism is the term from programming language.

if polycategory is unrelated,
I can try to develop a generalized theory based on my simple idea above.

I read through the page << Categorical models of dependent types >> on nLab.
it seems unsorted.
and the categorical model for dependent type system is a unsolved problem.

------
xieyuheng


On Wednesday, June 20, 2018 at 2:59:38 AM UTC+8, Matt Oliveri wrote:
>
> On Tuesday, June 19, 2018 at 4:07:34 AM UTC-4, xieyuheng wrote:
>>
>> I will learn more about polycategory and polymorphic,
>> and try to use them to explain dependent type system.
>>
>> thank you again :)
>>
>
> So polycategories had to do with the cut rule, which is not what your 
> examples are doing. I don't think you need to worry about polycategories. I 
> don't think there's much connection between polycategories and 
> polymorphism, other than the prefix "poly".
>
> The kind of polymorphism I used on your example is "row polymorphism". 
> This was already used for typing the "Cat" concatenative language. (So I 
> was guessing you already knew about it, otherwise I would've said so 
> earlier.) Thinking of the underlying monomorphic (non-polymorphic) stack 
> types as contexts, I figure the approach should generalize to dependent 
> contexts, with the operations being polymorphic substitutions between 
> dependent contexts.
>
> So I think the ingredients you want are some dependent generalization of 
> row polymorphism, and some categorical approach to interpreting the 
> underlying monomorphic contexts and substitutions, like contextual 
> categories.
>
> There are a lot of approaches to categorical interpretations of dependent 
> types, and I don't know very much about it. This overview page knows more 
> than I do:
> https://ncatlab.org/nlab/show/categorical+model+of+dependent+types
>

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

  reply	other threads:[~2018-06-20  6:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18 16:32 [HoTT] " xieyuheng
2018-06-18 18:58 ` [HoTT] " Matt Oliveri
2018-06-19  4:59   ` xieyuheng
2018-06-19  8:07   ` xieyuheng
2018-06-19 18:59     ` Matt Oliveri
2018-06-20  6:02       ` xieyuheng [this message]
2018-06-21 19:16         ` xieyuheng
2018-06-19  8:21   ` xieyuheng

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=ef21d057-acd4-4e5d-9411-5beaa2dc3195@googlegroups.com \
    --to=xyheme@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).