categories - Category Theory list
 help / color / mirror / Atom feed
From: selinger@mathstat.dal.ca (Peter Selinger)
To: joyal.andre@uqam.ca (Joyal, André)
Cc: categories@mta.ca (Categories List)
Subject: Re: Quipper: a quantum programming language
Date: Thu, 20 Jun 2013 16:36:47 -0300 (ADT)	[thread overview]
Message-ID: <E1Uplnf-0007SD-Tr@mlist.mta.ca> (raw)
In-Reply-To: <B3C24EA955FF0C4EA14658997CD3E25E6B2DBCAD@CAHIER.gst.uqam.ca>

Dear Andre,

the answer, unfortunately, is no. At least we don't think so. We
developed this programming language for IARPA, an agency of the
U.S. government, and effectively nobody knows whether they have a
quantum computer or not.

In any case, the language is designed so that it *could* run on a
quantum computer, if there was one. So now we are just standing by
until somebody builds the hardware :)

There is actually one kind of quantum computer that is already on the
market: the DWave quantum computer. Unfortunately, our language is not
compatible with it; the DWave machine uses a technology called
"adiabatic quantum computing", and people are still figuring out how
to program it. Our language would be compatible with quantum computers
based on the quantum circuit model.

Maybe the underlying point of your question is: why would anybody care
about a quantum programming language, when there is no quantum
computer?

One possible answer is: to help figure out how much it would actually
cost to build one. It is one thing for a quantum algorithm to appear
in a research paper. You will find a lot of statements like "it is
well-known that such-and-such can be done in O(n^2) operations", "by
applying such-and-such trick this problem can be reduced to another
problem with polynomial overhead", and so on. It is quite a different
thing to actually program the algorithm, and to worry about how to do
so efficiently. The difference between using 10^10 operations or 10^50
operations matters a lot in practice, but not in theory. Moreover, one
can then account for additional overhead that people don't usually
think about much, like the cost of adding many layers of error
correction, physical fail-safe mechanisms, and so on. By coding up
some algorithms for "realistic" problem sizes, we get a much better
idea of what kind of computing resources this would actually require.
("Realistic" can be defined as the problem size where a hypothetical
quantum computer would actually outperform a classical computer
running the best known classical algorithm for the problem).

Finally, there is some interesting theory that we can discover by
considering programming languages for quantum computing. To our
surprise, we even found a minor, yet satisfying, application of
identity types from type theory.

Best wishes, -- Peter

Joyal, Andr?? wrote:
>
> Dear Peter,
>
> I would like to ask you a naive question:
>
> Is it runned on an actual quantum computer?
>
>
> Best,
> Andr??
>

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


       reply	other threads:[~2013-06-20 19:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B3C24EA955FF0C4EA14658997CD3E25E6B2DBCAD@CAHIER.gst.uqam.ca>
2013-06-20 19:36 ` Peter Selinger [this message]
     [not found] <20130620193647.DBF5F8C0162@chase.mathstat.dal.ca>
2013-06-20 20:27 ` Joyal, André
2013-06-21  0:23   ` Peter Selinger
2013-06-19 19:40 Peter Selinger
2013-06-20 17:34 ` Joyal, André

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=E1Uplnf-0007SD-Tr@mlist.mta.ca \
    --to=selinger@mathstat.dal.ca \
    --cc=categories@mta.ca \
    --cc=joyal.andre@uqam.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).