Changes between Version 9 and Version 10 of Proposals/text

Timestamp:

11/06/10 11:54:05 (3 years ago)

Author:

dons (IP: 193.190.83.41)

Comment:

--

Proposals/text

@@ -1 @@
-= Proposal: Add Data.Text to the Haskell Platform =
+= Proposal: Add 'text' to the Haskell Platform =
 
 Proposal Author: Don Stewart
@@ -17 +17 @@
 Review comments should be sent to the libraries mailing list by
 October 1 so that we have time to discuss and resolve issues
-before the final deadline on November 1.
+before the final deadline for a call for consensus in early November.
 
     http://trac.haskell.org/haskell-platform/wiki/ReleaseTimetable 
@@ -168 +168 @@
 
  1. The `text-icu` package is not part of this proposal, as adding it would make the platform depend on the ICU C library. ''This is not a blocker.''
- 2. Both the `text` package and the `base` package provide Unicode encoding/decoding functionality. Perhaps some of this functionality could be merged. ''This cannot be achieved until the base library makes some types non-abstract. This is not a blocker.''
- 3. Some functions have similar names to functions in the [http://hackage.haskell.org/package/bytestring bytestring] package but have different types (other than `ByteString` vs `Text`.) Some functions have the same type but different names.
+ 2. Both the `text` package and the `base` package [http://www.haskell.org/pipermail/libraries/2010-September/014196.html provide Unicode encoding/decoding functionality]. Perhaps some of this functionality could be merged. ''This cannot be achieved until the base library makes some types non-abstract. This is not a blocker.''
+ 3. Naming inconsistencies between bytestring, text and list. Some functions [http://www.haskell.org/pipermail/libraries/2010-October/014614.html have similar names to functions] in the [http://hackage.haskell.org/package/bytestring bytestring] package but have different types (other than `ByteString` vs `Text`.) Some functions have the same type but different names.
  4. Do we need both a strict and lazy version of `Text`? The strict version needs one less indirection, can be unpacked in function arguments and takes less space when stored in data types. ''The performance difference is substantial, and the non-strict version can stream large quantities of data in a small footprint in a way not possible with the strict kind. Not a blocker.''
+
+=== On the naming issue ===
+
+ * One proposal on how to [http://www.haskell.org/pipermail/libraries/2010-October/014659.html fix the names], and the [http://www.haskell.org/pipermail/libraries/2010-October/014674.html author's response]
+
+''History'': updated [http://www.haskell.org/pipermail/libraries/2010-October/014532.html Oct 4, by johan]
 
 == Notes ==