-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Posix.io.bytestring module uses string instead of bytestring #63
Comments
This is by design, all that this module does it make it possible to open an FD with a Are you proposing to change the purpose of this module? |
More like I was digging into how I'd do posix pipes manipulation and was That makes sense. Thanks ! On Wednesday, June 1, 2016, Eric Mertens notifications@github.com wrote:
|
Eric Mertens notifications@github.com writes:
|
Agreed. That's probably a good idea. Better than staying maintainer On Wednesday, June 1, 2016, Ben Gamari notifications@github.com wrote:
|
@cartazio see top of http://hackage.haskell.org/package/unix-2.7.2.0/docs/System-Posix-ByteString.html
do we really have to replicate that paragraph in each and every finally, shameless self-plug: with AFPP we wouldn't need the |
I came across this just now and found it baffling too. I was expecting fdRead, fdWrite, et al, to operate on |
My opinion is that ByteString variants shouldn't mess with Whether that's a filepath or not doesn't really matter, does it? Most |
Essentially anything working through |
One of the bigger problems seems to be What to do here? Parametrize the type? Add a new type? I think the |
What does POSIX say about username / groupname? Is it just a bytestring with no encoding associated? Or is it supposed to be ASCII subset only? |
I can't see any mention of encoding. It seems it's only implicit that these are NUL terminated. No other guarantees. |
I think most of these instances are fixed. Some boring ones involving error types are still there, but not very interesting. I'll open a new ticket for GroupEntry/UserEntry. |
At least for the versions on hackage :(
The text was updated successfully, but these errors were encountered: