Changes between Version 8 and Version 9 of Proposals/text

Timestamp:

10/05/10 00:19:23 (3 years ago)

Author:

bos (IP: 38.99.63.41)

Comment:

--

Proposals/text

@@ -1 @@
-
 = Proposal: Add Data.Text to the Haskell Platform =
 
@@ -168 +167 @@
 == Open issues ==
 
- 1. The `text-icu` package is not part of this proposal, as adding it would make the platform depend on the ICU C library.
- 2. Both the `text` package and the `base` package provide Unicode encoding/decoding functionality. Perhaps some of this functionality could be merged.
+ 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.
- 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.
+ 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.''
 
 == Notes ==