You're reading the public-facing archive of the Category Theory Zulip server.
To join the server you need an invite. Anybody can get an invite by contacting Matteo Capucci at name dot surname at gmail dot com.
For all things related to this archive refer to the same person.
If someone tells me this diagram commutes, what do they actually mean? There are no parallel paths unless you consider the == bars as merging the objects into one, in which case there are infinitely-many parallel paths.
Screen-Shot-2021-07-22-at-5.07.05-pm.png
I think the ==es point outwards, so and symmetrically on the other side.
That’s what I’d pieced together. So it’s fair to say the diagram is malformed?
Maybe it would be clearer to note the direction on the ==es, but I also think it's somewhat standard to draw a diagram like this and make the reader infer the direction (particularly where there's only one direction that makes sense, like in this case).
Oh it’s a standard thing? I guess I’m going to continue to be baffled then, when I stumble onto diagrams like this. 😮
The use of c instead of a notation for the identity map confuses me too tbh
I imagine the idea here is to emphasize that , , and are equal as objects.
If we just write then that's hidden!
I believe this is standard notation, see e.g. the unit law for monads on Wikipedia. As in your example, the source, target, and direction of the arrows must be inferred.
Hm, that's a good example, thank you! I guess I'll have to get used to the notation.
Nick Smith said:
The use of c instead of a notation for the identity map confuses me too tbh
If our category has finite products, and we have a morphism , then we can denote the canonical morphism either as or . In the first case, we're using the functor and in the second case, we're using the functor . Of course, they have the same effect, so it doesn't matter which we use, and it becomes a matter of notation. I think it's helpful to note that both notations are entirely reasonable from this perspective.
Oh, so that's the logic behind it. I guess that makes sense, though still feels like an abuse of notation to me. It looks misleadingly like a binary operation.
It can be thought of as a binary operator. Remember that functors have actions on objects and morphisms. A bifunctor (i.e. a functor from a product category) therefore has actions on objects and morphisms in each argument. is the mixed action of a bifunctor, on the left side on an object, and on the right side on a morphism.
I thought a bifunctor would be accepting pairs of objects and pairs of morphisms... how does it make sense that it accepts one of each? The thing it spits out should be undefined.
Unless you're operating under the philosophy that objects and identity morphisms are the same thing.
It's a convenient abuse of notation, or it can be justified by what you just said. You could think of A as a shorthand for id_A. It really starts paying off when you're whiskering a 2-cell with a 1-cell, imo.
If you Curry the bifunctor, then you can mix objects and morphisms in applications.
You also want your definition of bifunctor to be compatible with a notion of currying: bifunctors should be equivalent to functors to the functor category, and in that case does associate to each object a functor