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.
I have a question related to my quest to understand closed categories:
If there is a monoidal structure on a category, you can use this to "multiply" two morphisms. For example, if I have and I can obtain . The morphism is guaranteed to exist by the bifunctor .
But there's also a bifunctor corresponding to the property of being monoidal closed. It's called the "internal hom functor", and has the form . I want to understand how this acts on pairs of morphisms, akin to above, but it's melting my brain. What does it mean to "raise one morphism to the power of another"? Are there any examples of how this works for simple categories? For Set perhaps? And is it actually a useful concept, or is it just a curiosity?
It is analogous to the hom-functor, so it acts by precomposition on the contravariant slot and by postcomposition on the covariant slot
i.e. sends a map to the map
Just a note: the notation usually refers to the pairing of two morphisms with the same domain. What you're describing is usually denoted .
Nick Smith:
And is it actually a useful concept, or is it just a curiosity?
I don't use it much myself, but it's theoretically very important because it shows the functor knows how morphisms are composed.
The formula Matteo gave illustrates this.
But be a bit careful with this formula! It makes perfect sense when , because it seems to be treating as a set of morphisms from to , with as an element of this set. (Matteo used upper-case letters for objects of but I'll use lower-case ones so I can say without making the universe collapse.)
But the concept of cartesian closed category is the most exciting precisely when the objects are not sets.
Nonetheless we can still define an 'element' of an object of , and any morphism gives an 'element' of . Do you know how this works?
Using this, Matteo's remark makes sense for arbitrary cartesian closed categories. Thus, the internal hom functor of a cartesian closed category always keeps track of how morphisms are composed. But it does more, too.
Matteo Capucci (he/him) said:
i.e. sends a map to the map
Wow, this is exactly the intuitive explanation I was looking for. That's so simple! I'm surprised all the resources on cartesian closed categories begin by waffling on about evaluation maps and adjunctions. None of the ones I've seen even bother to talk about this simple bifunctor. I think this example makes clear why closed categories are interesting.
So the composite allows you to "select" how you'd like to connect f to g (at least in ), and tells you what the end result is. It's like playing with lego!
John Baez said:
the concept of cartesian closed category is the most exciting precisely when the objects are not sets.
Yes, it seems the monoidal closed structure of is more interesting than ! I understand the internal hom functor for better than the one for (Poly is closed in two ways). It firstly tells you how a morphism constructs a composite (as above), but it also seems to tell you which "wire" () between directions in induced each wire in . It's an explanation: "here is why I'm connected the way I am". Of course, most people here probably aren't familar with ...
Nonetheless we can still define an 'element' of an object of , and any morphism gives an 'element' of . Do you know how this works?
I suppose I don't really know how gets encoded as an "element" of when we're talking about arbitrary categories, but I think I know how to point to these elements: you can use a map from the unit of the monoidal structure? For , this is the terminal object (thus ), and in the case of in , this is the monomial (thus ). But the objects may have additional properties that aren't captured by these maps alone, right?
Nick Smith said:
Matteo Capucci (he/him) said:
i.e. sends a map to the map
Wow, this is exactly the intuitive explanation I was looking for. That's so simple! I'm surprised all the resources on cartesian closed categories begin by waffling on about evaluation maps and adjunctions. None of the ones I've seen even bother to talk about this simple bifunctor.
It's not "waffling", since this fact follows from the more terse definition: a cartesian closed category is a cartesian category where each functor has a right adjoint.
Also, note that this fact is not sufficient to define the bifunctor , except in cases like where the object is a mere set, and is a mere function.
Here's where you should have been told this formula: when someone told you about the functor
which any category has. You need to know this functor to know what it means when people say
and are adjoint functors if there's a natural isomorphism
After all, you can't know what it means for this isomorphism to be natural until you know how is a functor - including what it does to morphisms!
John Baez said:
[...] the functor
which any category has. You need to know this functor to know what it means when people say
and are adjoint functors if there's a natural isomorphism
After all, you can't know what it means for this isomorphism to be natural until you know how is a functor - including what it does to morphisms!
When I first encountered adjunctions (a few months ago), they were explained in terms of "an isomorphism between sets", so the whole functor thing was swept under a rug.
Anyway, thank you for the clarifications. I'll continue studying these things. I really do appreciate being able to get help from experts. This Zulip is magical!
Nick Smith said:
John Baez said:
[...] the functor
which any category has. You need to know this functor to know what it means when people say
and are adjoint functors if there's a natural isomorphism
After all, you can't know what it means for this isomorphism to be natural until you know how is a functor - including what it does to morphisms!
When I first encountered adjunctions (a few months ago), they were explained in terms of "an isomorphism between sets", so the whole functor thing was swept under a rug.
It's good to think about why merely having an isomorphism of sets
is not enough for and to be adjoint functors. It really needs to be a natural isomorphism. Without naturality a lot of things go wrong when you try to actually use adjoint functors.
But to even state the naturality condition we need to explain how and are functors. And for that we need to explain how is a functor. So we need to understand what it does to morphisms.
A while back Jade and I were trying to construct the right adjoint to a functor , and we found a functor and an isomorphism of sets
So we thought we had found the right adjoint! But it turned out this isomorphism wasn't natural! So we had found the wrong adjoint.