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
I plan to use definitions from #666 for some development.
But definition Path
uses indexed datatype to define paths.
There were some issues with indexed datatypes in cubical agda mentioned in the past here and there, so I want to ask if I can expect such definition to be compatible with cubical machinery?
I can imagine doing this with Parametrized datatype, by adding necessary equations to the constructors. Is there any reason to believe that such additional bookkeeping may somehow pay off by better evaluation of expression with lots of Glue and transport? Or Is this only going to move complexity somewhere else?
The text was updated successfully, but these errors were encountered:
I plan to use definitions from #666 for some development.
But definition Path
uses indexed datatype to define paths.
There were some issues with indexed datatypes in cubical agda mentioned in the past here and there, so I want to ask if I can expect such definition to be compatible with cubical machinery?
I can imagine doing this with Parametrized datatype, by adding necessary equations to the constructors. Is there any reason to believe that such additional bookkeeping may somehow pay off by better evaluation of expression with lots of Glue and transport? Or Is this only going to move complexity somewhere else?
The text was updated successfully, but these errors were encountered: