Path to this page:
./
sysutils/hs-rawfilepath,
Use RawFilePath instead of FilePath
Branch: CURRENT,
Version: 1.1.0nb2,
Package name: hs-rawfilepath-1.1.0nb2,
Maintainer: pkgsrc-usersThe unix package provides RawFilePath which is a type synonym of
ByteString. Unlike FilePath (which is String), it has no performance issues
because it is ByteString. It has no encoding issues because it is
ByteString which is a sequence of bytes instead of characters.
That's all good. With RawFilePath, we can properly separate the "sequence
of bytes" and the "sequence of Unicode characters." The control is
yours. Properly encode or decode them with UTF-8 or UTF-16 or any codec of
your choice.
However,
* The functions in unix are low-level.
* The higher-level packages such as process and directory are strictly tied
to FilePath.
This library provides the higher-level interface with RawFilePath.
Master sites:
Filesize: 24.653 KB
Version history: (Expand)
- (2024-05-09) Updated to version: hs-rawfilepath-1.1.0nb2
- (2023-11-02) Updated to version: hs-rawfilepath-1.1.0nb1
- (2023-10-31) Package added to pkgsrc.se, version hs-rawfilepath-1.1.0 (created)
CVS history: (Expand)
2024-05-09 03:32:57 by Masatake Daimon | Files touched by this commit (1137) |
Log message:
Recursive revbump after changing the default Haskell compiler
|
2024-04-28 13:39:43 by Masatake Daimon | Files touched by this commit (1) |
Log message:
sysutils/hs-rawfilepath: Fix build with GHC 9.8
This breaks build with the currently default GHC 9.6. Please bear with me
until I switch the default compiler.
|
2023-11-02 07:37:49 by Masatake Daimon | Files touched by this commit (1141) |
Log message:
Revbump all Haskell after updating lang/ghc96
|
2023-10-31 17:20:00 by Masatake Daimon | Files touched by this commit (5) |
Log message:
sysutils/hs-rawfilepath: import hs-rawfilepath-1.1.0
The unix package provides RawFilePath which is a type synonym of
ByteString. Unlike FilePath (which is String), it has no performance issues
because it is ByteString. It has no encoding issues because it is
ByteString which is a sequence of bytes instead of characters.
That's all good. With RawFilePath, we can properly separate the "sequence
of bytes" and the "sequence of Unicode characters." The control is
yours. Properly encode or decode them with UTF-8 or UTF-16 or any codec of
your choice.
However,
* The functions in unix are low-level.
* The higher-level packages such as process and directory are strictly tied
to FilePath.
This library provides the higher-level interface with RawFilePath.
|