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

What should ev(I), id(I), etc do? #7

Open
jasonmorton opened this issue Apr 9, 2015 · 2 comments
Open

What should ev(I), id(I), etc do? #7

jasonmorton opened this issue Apr 9, 2015 · 2 comments

Comments

@jasonmorton
Copy link
Owner

If we use uniformscaling, we don't know the type, need uniformsclaing morphism id(I) that these can be equal to. If we choose correctly, transpose will work as used with the id(I) and coev(I) even when applied to f:I->A. Will require special casing otimes of MWords to look for id(I). Stopgap is to special case transpose.

@jasonmorton
Copy link
Owner Author

Strict fts should collapse them
Lax fts should leave in
Otherwise the meaning of id(I) should be delegated to the quantitative category. I is mapped to the munit of Q. Then id(munit(Q)) is called. Usually it is multiplication by one, or empty box, etc.
No uniform scaling unless Q uses it as the monoidal unit.

@jasonmorton
Copy link
Owner Author

Careful about rewriting border: should composing with idA or idI be automatically collapsed? Prob not

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

No branches or pull requests

1 participant