categories - Category Theory list
 help / color / mirror / Atom feed
From: Patrik Eklund <peklund@cs.umu.se>
To: categories@mta.ca
Subject: Re: Martin-Lof type theory gentle introduction please
Date: Tue, 04 Feb 2014 06:46:58 +0200	[thread overview]
Message-ID: <4eca2e8be821b8858306fab50b823a4c@cs.umu.se> (raw)
In-Reply-To: <E1WATBX-0000hk-9i@mlist.mta.ca>

Hi Vasili,

This is not an easy one, since that "theory" has changed form every now
and then.

I cannot but see it as related to the unsolved issue of the distinction
between terms and sentences in logic. When we mix the two, or when we
are unclear of the "types" of the two, we will not be able to proceed.

Church in 1940 spoke about the 'iota' and 'o' "types of types", where
'iota' is potentially the type of possible sorts in a "conventional
signatures". Then 'o' is the "type of propositions", but Church was
humble to say that the formal situation about this is not clear. In my
view this has not been properly solved since then. See our "Modern eyes
on lambda-calculus" under GLIOC (www.glioc.com) for a notion of a
three-level signature that may be a solution to some of the problems in
this context.

Martin-L??f started off with a universes V of types, and added an "axiom"
saying "V is also a type", i.e. is part of that V, so "V \in V" was seen
to be ok. It turned out not to, so later it was changed by others to
"Prop \in Type", where Type is like Church's iota and Prop like Church's
o. This still doesn't distinguish between terms and sentences in a
proper way, and type constructors kind of come to rescue "from the
outside" and are indeed not "internalized" within any signature.
Dependent data typing is full of that "externalization".

Howards 1969 note (circulated among a few, eventually published upon
request by 1980) on the subject is also fine, continuing e.g. what Curry
and Fey wrote a decade before, but these notes and writings also do not
conclude anything about Church's dilemma about iota and o. Needless to
say, Heyting's book is "set-theoretic" so it doesn't help at all. I
don't know the "type theory" history and atmosphere from the time of
around 1965 (I was seven years old at that time), but I can imagine that
there was a bit of "fictive mathematics" and ambitions to establish "new
foundations" around tables here and there at that time and during the
next decade or even two. Whether this has been useful or harmful for
computer science as a whole is difficult to say, but obviously, lots of
functional languages have been created upon different views of those
"axioms". Many definitely say it has all been very useful, but I have
started to have "foundational and constructive doubts", at the age of
55. "Imperative" and "algorithm" is still allowed to be "outside
everything", and this privilege is quite "interesting?", but also
doubtful. You may want to recall e.g. what Kleene said in his
Metamathematics about the "metamathematical proposition" R(x,Y): "There
must be a decision procedure or algorithm for the question whether
R(x,Y) holds". Indeed there must be. Otherwise G??del's "theorems" are
doubtful. Maybe G??del's "theorems" are basically paradoxes, showing how
obscure the foundations really are. Freely making propositions related
to truth and provability, and feeling privileged not to keep concepts
clearly apart from each other, i.e. "mixing bags", leads to many things,
but also leads to trouble.

Even concerning the distinction between term and sentence, I strongly
believe we need to be formal firstly about the term monad (see "Fuzzy
terms" under GLIOC), in order to be "constructive" about terms.
Thereafter we quickly realize that terms actually reside in sentences.
Substitution and compositions with it is for terms, not for sentences.
There is a certain "lativity" in all this, and "lativity of choice" if
you want to be foundational about it. I don't think there is a "unique"
or "canonic" foundations.

Basically I am not sure you will find that gentle "tutorial", but if you
do, I would also be interested to read it. However, a potpourri tutorial
or paper is no good, because the light will just keep staying out,
leaving me in the dark, and even worse, in the "foundational gutter".

Cheers,

Patrik

-- 
Prof. Patrik Eklund
Ume?? University
Department of Computing Science
SE-90187 Ume??
Sweden

-------------------------

mobile: +46 70 586 4414
website: www8.cs.umu.se/~peklund
Skype: patrikeklund
Adobe Connect: https://connect.sunet.se/patrikeklund/



[For admin and other information see: http://www.mta.ca/~cat-dist/ ]


  reply	other threads:[~2014-02-04  4:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03  1:51 Vasili I. Galchin
2014-02-04  4:46 ` Patrik Eklund [this message]
2014-02-06 12:49 ` Yoshiki Kinoshita (nifty)
2014-02-07 14:34 ` matias
2014-02-09 18:16   ` Mike Stay
2014-02-11 19:08 ` Urs Schreiber

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=4eca2e8be821b8858306fab50b823a4c@cs.umu.se \
    --to=peklund@cs.umu.se \
    --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).