From 23b85bb52cdc05471aae45e04e67ac4a647e322b Mon Sep 17 00:00:00 2001
From: ben <benjaminlgreenman@gmail.com>
Date: Mon, 14 Mar 2016 02:18:59 -0400
Subject: [PATCH] [icfp] add singletons cite
---
icfp-2016/bib.rkt | 7 +++++++
icfp-2016/intro.scrbl | 2 +-
2 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/icfp-2016/bib.rkt b/icfp-2016/bib.rkt
index e22f014..ea2caf1 100644
--- a/icfp-2016/bib.rkt
+++ b/icfp-2016/bib.rkt
@@ -1137,3 +1137,10 @@
#:author "Matthew Flatt"
#:location (proceedings-location icfp #:pages '(72 83))
#:date 2002))
+
+(define ew-haskell-2012
+ (make-bib
+ #:title "Dependently Typed Programming with Singletons"
+ #:author "Richard A. Eisenberg and Stephanie Weirich"
+ #:location (proceedings-location haskell #:pages '(117 130))
+ #:date 2012))
diff --git a/icfp-2016/intro.scrbl b/icfp-2016/intro.scrbl
index 5aac8a3..d24896f 100644
--- a/icfp-2016/intro.scrbl
+++ b/icfp-2016/intro.scrbl
@@ -31,7 +31,7 @@ The above are all @emph{value errors} that depend on properties not expressed
by Haskell's standard list, integer, and string datatypes.
Even so, it is obvious to the programmer that the expressions will go wrong
and there have been many proposals for detecting these and other value
- errors@~cite[a-icfp-1999 ddems-icse-2011 lb-sigplan-2014].
+ errors@~cite[a-icfp-1999 ddems-icse-2011 ew-haskell-2012 lb-sigplan-2014].
What stands between these proposals and their adoption is the complexity or
annotation burden they impose on language users.