From: Toby Bartels <toby+categories@ugcs.caltech.edu>
To: categories@mta.ca
Subject: Re: Cartesian closed without products
Date: Mon, 7 Jan 2008 13:35:11 -0800 [thread overview]
Message-ID: <E1JCJ0o-0005w1-Sb@mailserv.mta.ca> (raw)
Richard Garner wrote:
>On reflection, [...]
>EK-closed requires the unit object to be representable as
>well.
This is a reasonable requirement anyway,
since the unit is the 0fold iterated hom,
just as it's the 0fold iterated product.
So if you think <closed under binary products>
should be accompanied by <with a unit object>,
then so should <closed under internal homs>.
OTOH, the version without unit probably has some use,
just as non-monoid semigroups occasionally do.
--Toby
next reply other threads:[~2008-01-07 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 21:35 Toby Bartels [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-09 2:29 Toby Bartels
2008-01-09 1:36 Peter Selinger
2008-01-08 21:29 Ronnie
2008-01-07 14:09 Richard Garner
2008-01-07 11:08 Richard Garner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1JCJ0o-0005w1-Sb@mailserv.mta.ca \
--to=toby+categories@ugcs.caltech.edu \
--cc=categories@mta.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).