From: Francois Pottier <Francois.Pottier@inria.fr>
To: types-announce@lists.seas.upenn.edu,
Caml Mailing List <caml-list@yquem.inria.fr>,
smlnj-dev-list@lists.sourceforge.net, MLton-user@mlton.org,
haskell@haskell.org
Subject: [ANN] Call for participation: TLDI'07
Date: Tue, 14 Nov 2006 10:57:19 +0100 [thread overview]
Message-ID: <20061114095719.GA6734@yquem.inria.fr> (raw)
******************************************************************************
The 2007 ACM SIGPLAN Workshop on
Types in Language Design and Implementation
(TLDI'07)
Affiliated with the 34th ACM SIGPLAN-SIGACT Symposium on
Principles of Programming Languages
(POPL'07)
Call for Participation
http://www.cs.berkeley.edu/~necula/tldi07/
******************************************************************************
Preliminary programme
Invited talks:
Kathleen Fisher (AT&T Research)
Conor McBride (University of Nottingham)
Accepted papers:
A Garbage-Collecting Typed Assembly Language
Chris Hawblitzel, Heng Huang, Lea Wittie and Juan Chen
A graphical presentation of MLF types with a linear-time unification algorithm
Didier Rémy and Boris Yakobowski
An Open Framework for Foundational Proof-Carrying Code
Xinyu Feng, Zhaozhong Ni, Zhong Shao and Yu Guo
Modular Information Hiding and Type-Safe Linking for C
Saurabh Srivastava, Michael Hicks and Jeffrey Foster
Semantics of an Effect Analysis for Exceptions
Nick Benton and Peter Buchlovsky
System F with Type Equality Coercions
Martin Sulzmann, Manuel Chakravarty, Simon Peyton Jones and Kevin Donnelly
******************************************************************************
Scope
The role of types and proofs in all aspects of language design, compiler
construction, and software development has expanded greatly in recent
years. Type systems, type analyses, and formal deduction have led to new
concepts in compilation techniques for modern programming languages,
verification of safety and security properties of programs, program
transformation and optimization, and many other areas. In light of this
expanding role of types, the ACM SIGPLAN Workshop on Types in Language Design
and Implementation (TLDI'07) follows five previous International Workshops on
types in compilation and language design (TIC'97, TIC'98, TIC'00, and TLDI'03
and TLDI'05), with the hope of bringing together researchers to share new
ideas and results in this area.
******************************************************************************
General Chair
François Pottier
INRIA Rocquencourt
BP 105
78153 Le Chesnay Cedex
FRANCE
francois.pottier@inria.fr
Program Chair
George Necula
University of California
783 Soda Hall
Berkeley, CA 94720
necula@cs.berkeley.edu
Program Committee
Damien Doligez, INRIA
Peter Lee, Carnegie Mellon University
Andrew Kennedy, Microsoft Research, Cambridge
Naoki Kobayashi, Tohoku University
George Necula (chair), University of California, Berkeley
Randy Pollack, Edinburgh University
Norman Ramsey, Harvard University
David Tarditi, Microsoft Research, Redmond
Stephanie Weirich, University of Pennsylvania
Hongwei Xi, Boston University
reply other threads:[~2006-11-14 9:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20061114095719.GA6734@yquem.inria.fr \
--to=francois.pottier@inria.fr \
--cc=MLton-user@mlton.org \
--cc=caml-list@yquem.inria.fr \
--cc=haskell@haskell.org \
--cc=smlnj-dev-list@lists.sourceforge.net \
--cc=types-announce@lists.seas.upenn.edu \
/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