From: Stephanie Weirich <sweirich@cis.upenn.edu>
To: Haskell List <haskell@haskell.org>,
coq-club@inria.fr, caml-list@yquem.inria.fr,
types-announce@lists.seas.upenn.edu, agda@lists.chalmers.se,
mlton-user@mlton.org, eapls@jiscmail.ac.uk,
nj-pls@lists.seas.upenn.edu, sml-evolution@cs.uchicago.edu
Cc: Derek Dreyer <dreyer@mpi-sws.org>,
STEPHANIE WEIRICH <sweirich@cis.upenn.edu>
Subject: TLDI 2011 Call for participation
Date: Tue, 30 Nov 2010 16:17:57 -0500 [thread overview]
Message-ID: <C3976031-0C81-4EFC-AD8B-EA841A96F72B@cis.upenn.edu> (raw)
*********************************************************************
CALL FOR PARTICIPATION
TLDI 2011
ACM SIGPLAN Workshop on
Types in Language Design and Implementation
25 January 2011
Austin, TX, USA
To be held in conjunction with POPL 2011
http://www.mpi-sws.org/~dreyer/tldi2011/
*********************************************************************
IMPORTANT DATES
Deadline for student travel grant applications: December 17, 2010
Hotel reservation deadline: December 21, 2010
Notification of student travel awards: December 27, 2010
Early registration deadline: December 31, 2010
VENUE
TLDI'11 and all POPL'11 affiliated events will take place at the
Omni Austin Hotel in downtown Austin, TX.
REGISTRATION
To register for TLDI'11, follow the link from the POPL 2011 page, at
https://regmaster3.com/2011conf/POPL11/register.php
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-based analyses and type-theoretic
deductive systems have been central to advances in compilation
techniques for modern programming languages, verification of safety
and security properties of programs, program transformation and
optimization, and many other areas. The ACM SIGPLAN Workshop on Types
in Language Design and Implementation brings researchers together to
share new ideas and results concerning all aspects of types and
programming, and is now an annual event.
WORKSHOP PROGRAM
Session 1: Invited Talk (9:30 - 10:30)
Type Design Patterns for Computer Mathematics
Georges Gonthier (Microsoft Research, Cambridge)
Break (10:30-11:00)
Session 2 (11:00-12:30)
Singleton: A General-Purpose Dependently-Typed Assembly Language
Simon Winwood and Manuel Chakravarty
A Type and Effect System for Deadlock Avoidance in
Low-Level Languages
Prodromos Gerakios, Nikolaos Papaspyrou and Konstantinos Sagonas
Extended Alias Type System using Separating Implication
Toshiyuki Maeda, Haruki Sato and Akinori Yonezawa
Lunch (12:30-14:30)
Session 3: Invited Talk (14:30-15:30)
Type Safety from the Ground Up
Chris Hawblitzel (Microsoft Research, Redmond)
Break (15:30-16:00)
Session 4 (16:00-17:30)
AuraConf: A Unified Approach to Authorization and Confidentiality
Jeffrey Vaughan
Information Flow Enforcement in Monadic Libraries
Dominique Devriese and Frank Piessens
The Essence of Monotonic State
Alexandre Pilkiewicz and François Pottier
reply other threads:[~2010-11-30 21:18 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=C3976031-0C81-4EFC-AD8B-EA841A96F72B@cis.upenn.edu \
--to=sweirich@cis.upenn.edu \
--cc=agda@lists.chalmers.se \
--cc=caml-list@yquem.inria.fr \
--cc=coq-club@inria.fr \
--cc=dreyer@mpi-sws.org \
--cc=eapls@jiscmail.ac.uk \
--cc=haskell@haskell.org \
--cc=mlton-user@mlton.org \
--cc=nj-pls@lists.seas.upenn.edu \
--cc=sml-evolution@cs.uchicago.edu \
--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