From: dusko pavlovic <dusko@hawaii.edu>
To: Mike Stay <metaweta@gmail.com>
Cc: categories <categories@mta.ca>
Subject: Re: Evaluation of source code, category theoretically?
Date: Thu, 23 Jan 2014 13:30:13 -1000 [thread overview]
Message-ID: <A79AC73D-EEDF-41DA-A6D3-6D18D4255AA6@hawaii.edu> (raw)
In-Reply-To: <E1Vz3nm-0006bf-1B@mlist.mta.ca>
i am hoping that you might also like monoidal computer
http://arxiv.org/abs/1208.5205
it's similar to robin's turing categories, but also quite different. it's all in string diagrams. there is also a complexity theory paper, with a much better string diagram language, which i still didn't upload on arxiv, but will do soon. comments welcome and appreciated.
-- dusko
On Jan 2, 2014, at 8:05 AM, Mike Stay <metaweta@gmail.com> wrote:
> What's the right way to think about evaluation in category theory?
> I'm guessing it will look kind of like this: the category will be
> symmetric monoidal closed and equipped with an object S whose points
> are "source code", together with a collection of interpreter
> epimorphisms
> run_{X, Y}: S -> [X, Y]
> and some notion of composition in S that works well with composition
> of morphisms.
>
> What are the right keywords for doing a literature search on this?
> --
> Mike Stay - metaweta@gmail.com
> http://www.cs.auckland.ac.nz/~mike
> http://reperiendi.wordpress.com
>
>
> [For admin and other information see: http://www.mta.ca/~cat-dist/ ]
[For admin and other information see: http://www.mta.ca/~cat-dist/ ]
next prev parent reply other threads:[~2014-01-23 23:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 18:05 Mike Stay
2014-01-23 23:30 ` dusko pavlovic [this message]
2014-01-03 17:46 Greg Meredith
[not found] <CAKQgqTYam=YUD5uvLxPu3HkMe=gSirKgGqKnoq0Rx_mkYdK7jw@mail.gmail.com>
2014-01-04 20:48 ` Mike Stay
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=A79AC73D-EEDF-41DA-A6D3-6D18D4255AA6@hawaii.edu \
--to=dusko@hawaii.edu \
--cc=categories@mta.ca \
--cc=metaweta@gmail.com \
/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).