| 170 | | The text-icu package is not part of this propposal. |
| | 170 | 1. The `text-icu` package is not part of this proposal, as adding it would make the platform depend on the ICU C library. |
| | 171 | 2. Both the `text` package and the `base` package provide Unicode encoding/decoding functionality. Perhaps some of this functionality could be merged. |
| | 172 | 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. |
| | 173 | 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. |
