-
Notifications
You must be signed in to change notification settings - Fork 12
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
Constant square in redtt #239
Comments
The diagonal definitely can't be |
Hahaha, good point Evan! If you get it to be |
Here's a (slightly more general) solution that is the size of two connections:
|
Very nice and fast answer! Thanks Evan. One thing that confuses me is the use of "comp"... aren't all of the compositions homogeneous? |
I believe that the surface syntax |
Cool! Just a minor remark: I'm getting very owned by |
changed to an |
Thanks! Now I see how your cube looks. Note that the number of calls to comp in this term is 9. I wonder if this will lead to performance issues (imagine if A is a line in U...). |
Here's a more direct solution which uses 7 comps:
|
Here's one that uses 5:
|
I missed the party. The same trick used by the pseudo-connections still applies, and all the current pseudo-connections should be replaced by Evan's last solution immediately. |
Actually, what I said was dumb. The current pseudo-connections are simpler and more powerful (with the correct diagonal) than the instances of Evan's final construction. |
Here's a small puzzle that we will need to solve by next week: given
p : Path A a a
construct a square withp
everywhere on the boundary.In cubicaltt this uses lots of connections/reversals:
https://github.com/mortberg/cubicaltt/blob/master/examples/prelude.ctt#L165
We would definitely want to avoid just copying this as it will be pretty huge without native connections/reversals. Can someone come up with a direct definition like the one used for connections?
I don't think it's important what the diagonal is, but if you can get it to be
p
as well then you get a bonus point!The text was updated successfully, but these errors were encountered: