[Haskell-cafe] [ANN] stdio-0.1.0.0 - A simple and high performance IO toolkit for Haskell

[Brandon Allbery]

I'd like to point out that using unpinned memory for your ByteString
alternative means you aren't providing the same API: as most string-using
foreign functions expect something more like a bytestring than a Haskell
string or text type, ByteString is pinned specifically to support that use
case directly and many users of ByteString expect that support. This will
include the ByteString variants of various functions in the "posix"
package, which are thereby providing "raw" versions of system calls,
ensuring the Haskell program can get exactly what the OS provides (POSIX
interfaces don't use Unicode, thus various Unicode encodings can be unable
to provide the exact OS level representation of e.g. file names).

On Sat, Feb 16, 2019 at 9:30 AM Joachim Durchholz <jo at durchholz.org> wrote:

> Am 16.02.19 um 13:23 schrieb 寒东:
> > Some unicode processing such as normalization and casefolding is also
> provide, based on a C unicode libraryutf8rewind  <
> https://bitbucket.org/knight666/utf8rewind>.
>
> FWIW the rest looks fine, but committing to a specific UTF-8
> implementation is risky. Unicode is a large and complicated standard,
> and constantly evolving; I am sceptical that a one-man library like
> utf8rewind can keep up with that, and I'd wrap a mature Unicode library
> (such as ICU) rather than place my bet on a one-man show like utf8rewind.
>
> In particular, I'd avoid utf8rewind because the author believes that
> deviating from a standard improves security.
> (See his comment in
>
> https://bitbucket.org/knight666/utf8rewind/issues/8/length-function-should-not-use-strlen
> .)
> I do not think that's a well-considered policy, and certainly does not
> make me think that his code is well-audited. Including such a thing in
> such a basic library as stdio seems unwise to me.
>
> > To make our package more useful, we rebuild Builder and Parser type from
> groud, add TCP socket and filesystem support, so that user can start using
> it to do some simple task, such as parsing a CSV file or starting a TCP
> server and communicate in protocols. We also provide high performance timer
> and logger module, which is useful in practical engineering tasks.
>
> You should split the library, into stuff that does fast byte shoving,
> and into stuff that does fast byte processing.
> That way, things can start to improve and evolve independently.
>
> > For installation guide and examples, please see the project's README. As
> we (I and Tao He) both are not native english speakers, the document
> quality is not as satisfying as it can be, please help!
>
> Judging from this message, your English seems pretty good actually :-)
>
> Regards,
> Jo
> _______________________________________________
> Haskell-Cafe mailing list
> To (un)subscribe, modify options or view archives go to:
> http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
> Only members subscribed via the mailman list are allowed to post.



-- 
brandon s allbery kf8nh
allbery.b at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.haskell.org/pipermail/haskell-cafe/attachments/20190216/6b008f8f/attachment.html>