| ... | ... | @@ -3,7 +3,7 @@ |
|
|
|
## Brief Explanation
|
|
|
|
|
|
|
|
|
|
|
|
Haskell source code uses the Unicode character set. However, current implementations either support only one encoding (e.g. UTF-8), or require the encoding to be signified via out-of-band means, which makes Haskell source code non-portable.
|
|
|
|
Haskell source code uses the Unicode character set. However, current implementations either support only one encoding (e.g. UTF-8), or require the encoding to be signified via out-of-band means, which makes Haskell source code outside ASCII range non-portable.
|
|
|
|
|
|
|
|
|
|
|
|
This proposal outlines a detection heuristics that categorizes the source code as under UTF-8, UTF-16 or UTF-32. A conforming Haskell-prime implementation must accept UTF-8 and UTF-16, and may fail on UTF-32 input.
|
| ... | ... | @@ -73,7 +73,9 @@ gracefully handle two common class of text editor flaws: |
|
|
|
## Pros
|
|
|
|
|
|
|
|
- Ensures uniform treatment of Unicode in source code.
|
|
|
|
- Disallows implicit ISO-8859-\* encodings in source code, ensuring portability.
|
|
|
|
|
|
|
|
## Cons
|
|
|
|
|
|
|
|
- Mandating a minimum support for UTF-8/UTF-16 places an implementation burden on compiler writers.
|
|
|
|
- Existing code relying on a non-UTF8, locale-/implementation-specific encoding will need conversion. |
