You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: TypeTheory/ALV1/CwF_SplitTypeCat_Cats_Standalone.v
+33-28Lines changed: 33 additions & 28 deletions
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@
8
8
9
9
This file defines the categories of term-structures and _q_-morphism structures over a fixed object-extension structure, and proves that they are univalent and equivalent.
10
10
11
-
For the more interesting case where the object-extension structure is also allowed to vary, see [CwF_Split_TypeCat_Cats], where this more general category is constructed, using the formalism of displayed categories.
11
+
For the more interesting case where the object-extension structure is also allowed to vary, see [CwF_Split_TypeCat_Cats], where this more general category is constructed, using the formalism of displayed categories, and [CwF_SplitTypeCat_Equiv_Cats], giving the equivalence in the displayed setting.
12
12
13
13
In general, this file should be deprecated, and the displayed version should be used for all further development. This standalone version is included just to give the equivalence in a form independent of the development of displayed categories.
etrans. use (toforallpaths (!nat_trans_ax (term_fun_mor_TM _) _)).
344
+
etrans. apply pathsinv0, nat_trans_ax_pshf.
340
345
etrans. cbn. apply maponpaths, @pathsinv0, W.
341
346
etrans. apply term_fun_mor_te.
342
347
apply W'.
@@ -373,12 +378,11 @@ Lemma term_from_qq_mor
373
378
: (Y --> Y').
374
379
Abort.
375
380
376
-
(* TODO: rename and move this section! *)
381
+
(* TODO: rename and upstream this section! *)
377
382
Section Rename_me.
378
383
(* TODO: naming conventions in this section clash rather with those of [ALV1.CwF_SplitTypeCat_Equivalence]. Consider! *)
379
-
(* TODO: one would expect the type of this to be [nat_trans_data]. However, that name breaks HORRIBLY with general naming conventions: it is not the _type_ of the data (which is un-named for [nat_trans]), but is the _access function_ for that data! Submit issue for this? *)
0 commit comments