Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependent Composition #144

Open
wants to merge 41 commits into
base: main
Choose a base branch
from

Conversation

thchatzidiamantis
Copy link
Contributor

No description provided.

@thchatzidiamantis thchatzidiamantis marked this pull request as draft June 21, 2024 16:43
@thchatzidiamantis thchatzidiamantis marked this pull request as ready for review June 21, 2024 20:00
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you really want to add this line about agdaLanguageServer?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know how this ended up here, I assume I should just delete it.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fizruk can you comment on this?

along an arrow f : hom A x y to give a term in C y.

```rzk title="RS17, covariant transport from beginning of Section 8.2"
#def covariant-transport
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are you removing this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I go to my repository this is in my file, other things above it were removed. Again, don't know what is happening.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be an issue about which branch you are.

Copy link
Contributor Author

@thchatzidiamantis thchatzidiamantis Jun 21, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is also still in the file we are now if you expand it, starting at line 702. I can delete all of this and start a new PR if this is all too messy.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see you moved it. Sorry you are right.

@nimarasekh
Copy link
Collaborator

Why does this PR have such an exciting history (closed, reopened, marked draft, ... )

@emilyriehl
Copy link
Collaborator

The code looks great. I've suggested a few renamings (feel free to push back @thchatzidiamantis). Let's also have someone else figure out what happened with the agda thing in the settings file.

@jonweinb
Copy link
Collaborator

jonweinb commented Jul 9, 2024

Great work @thchatzidiamantis and @nimarasekh!

I also have a version for a more general setting over in the yoneda repo, not yet integrated into sHoTT: https://github.com/emilyriehl/yoneda/blob/master/src/simplicial-hott/12-cocartesian.rzk.md
Happy to do that soon, and coordinate as appropriate.

@nimarasekh
Copy link
Collaborator

The code looks great. I've suggested a few renamings (feel free to push back @thchatzidiamantis). Let's also have someone else figure out what happened with the agda thing in the settings file.

Did you commit these changes you are suggesting or is something wrong on my side? Cause I can't see them.

@nimarasekh
Copy link
Collaborator

Great work @thchatzidiamantis and @nimarasekh!

I also have a version for a more general setting over in the yoneda repo, not yet integrated into sHoTT: https://github.com/emilyriehl/yoneda/blob/master/src/simplicial-hott/12-cocartesian.rzk.md Happy to do that soon, and coordinate as appropriate.

I think all the work here is @thchatzidiamantis with tremendous help by @emilyriehl and nothing by me. Also yeah you should add your result to the library, why not?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fizruk can you comment on this?


We can compose dependent arrows given a covariant type family.

```rzk title="RS17, Remark 8.11"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd move this label down to the definition of dcomp, since "is-contr-ext-is-covariant" is proving contractibility of a different type than is discussed there (which is fine).

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The name "is-covariant-family-is-segal-base" is used for some definitions that depend on both of these hypotheses but not for all of them (some just use "is-covariant"). I'd add it to all the definitions here that use these hypotheses.

If this is too long perhaps "is-covariant-is-segal" could work everywhere. But I'd adopt whatever convention uniformly.

We can compose dependent arrows given a covariant type family.

```rzk title="RS17, Remark 8.11"
#def is-contr-ext-is-covariant uses (extext)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

perhaps "ext" should be "horn-ext"; as revealed by the proof, up to equivalence, this proves contractibility of horn extension (into a sigma type).

A C is-covariant-C is-segal-A)
( \ t → (a t , c t)))

#def equiv-ext-is-segal-base
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Similarly perhaps "ext" should be "comp-horn-ext". Here I've added "comp" because this is a special case of the sort of horns considered above (over a composition witness in the base). This also differentiates the term below.

( witness-comp-is-segal A is-segal-A (a (0₂ , 0₂)) (a (1₂ , 0₂))
( a (1₂ , 1₂)) (\ s → a (s , 0₂)) (\ s → a (1₂ , s)))

#def is-contr-horn-ext-is-covariant uses (extext)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the above renamings are adopted then perhaps "horn-ext" is "comp-horn-ext".

( s ≡ 0₂ ↦ ff t
, t ≡ 1₂ ↦ gg s)

#def compositions-are-dhorn-fillings
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe "dcompositions-are-dhorn-fillings"?

( is-contr-ext-dhom-is-covariant
A is-segal-A C is-covariant-C x y z f g u v w ff gg)))
```

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need to leave an rzk code block here unless you want to add a comment (eg "Like ordinary composition, dependent composition is unique."

@thchatzidiamantis
Copy link
Contributor Author

Updated the names as suggested by @emilyriehl.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants