From: "Daniel R. Grayson" <danielrich...@gmail.com>
To: Homotopy Type Theory <HomotopyT...@googlegroups.com>
Subject: Re: Vladimir Voevodsky
Date: Thu, 12 Oct 2017 12:06:20 -0700 (PDT) [thread overview]
Message-ID: <69c716dc-7fbf-4c07-a128-21c75fc996da@googlegroups.com> (raw)
In-Reply-To: <ab74b6db-d7aa-42cc-aa78-87d3c90c998e@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 1545 bytes --]
This email from Vladimir seems to be from a time when he had just learned
more about Coq but had not yet started using it:
From: "Vladimir Voevodsky" <vlad...@ias.edu>
Subject: Re: theorem proving
Date: Wed, December 30, 2009 10:34 am
To: "Daniel R. Grayson" <d...@math.uiuc.edu>
Hi Dan,
thanks for the link. I have heard about this one (from coq-club actually on
which list I am since several years ago). All is well with me, all of the
Bloch-Kato papers are submitted to journals for about a year now and many
are
accepted.
I am thinking a lot these days about foundations of math and automated proof
verification. My old idea about a "univalent" homotopy theoretical models of
Martin-Lof type systems survived the verification stage an I am in the
process of writing things up.
I also took a course at the Princeton CS department which was for most part
about Coq and was very impressed both by how much can be proved in it in a
reasonable time and by how many young students attended (45, 35 undergrad +
10 grad!).
How are you?
Vladimir.
On Dec 29, 2009, at 8:43 PM, Daniel R. Grayson wrote:
> Volodya,
>
> This seems to be a good theorem proving conference to attend this summer:
>
> https://sympa-roc.inria.fr/wws/arc/coq-club/2009-12/msg00057.html
>
> Call for Papers
> ITP 2010: Conference on Interactive Theorem Proving
> 11-14 July 2010, Edinburgh, Scotland
> http://www.floc-conference.org/ITP-cfp.html
>
> I hope all is well for you.
>
> Dan
[-- Attachment #1.2: Type: text/html, Size: 2196 bytes --]
next prev parent reply other threads:[~2017-10-12 19:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-01 4:25 Daniel R. Grayson
2017-10-01 4:54 ` Daniel R. Grayson
2017-10-01 8:07 ` [HoTT] " Thomas Streicher
2017-10-01 13:18 ` Peter LeFanu Lumsdaine
2017-10-01 15:06 ` Joyal, André
2017-10-01 14:48 ` [HoTT] " Steve Awodey
2017-10-01 17:08 ` Andrei Rodin
2017-10-01 20:06 ` [HoTT] " Nicolai Kraus
2017-10-01 20:08 ` Chris Kapulkin
2017-10-02 13:20 ` Marcelo Fiore
2017-10-02 14:00 ` Andrew Polonsky
2017-10-02 15:22 ` [HoTT] " Andrej Bauer
2017-10-04 22:52 ` Martín Hötzel Escardó
2017-10-05 4:52 ` [HoTT] " Gershom B
2017-10-05 6:08 ` Timothy Carstens
2017-10-05 10:41 ` [HoTT] " Thierry Coquand
2017-10-05 13:38 ` Daniel R. Grayson
2017-10-06 5:41 ` [HoTT] " Michael Shulman
2017-10-11 15:26 ` Daniel R. Grayson
2017-10-11 17:47 ` Daniel R. Grayson
2017-10-11 19:06 ` [HoTT] " Steve Awodey
2017-10-12 19:06 ` Daniel R. Grayson [this message]
2017-10-12 19:24 ` Daniel R. Grayson
2017-10-12 21:55 ` Martín Hötzel Escardó
2017-10-12 22:21 ` [HoTT] " Michael Shulman
2017-10-14 21:12 ` Martín Hötzel Escardó
2017-10-14 21:20 ` Martín Hötzel Escardó
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=69c716dc-7fbf-4c07-a128-21c75fc996da@googlegroups.com \
--to="danielrich..."@gmail.com \
--cc="HomotopyT..."@googlegroups.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).