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
Improve ByteString safety and add [isValid, normalise, equalFilePath] functions #17
Conversation
Don't use OverloadedStrings, which can depend on GHC behavior. Also use the word8 package for safe word8 literals.
This also drops the old _equalFilePath function.
Is this project still active? |
@JohnLato Do you actively maintain |
I guess I'll fork this library on hackage then. |
I've pinged him on email just now. |
I've forked this library (along with the path library) into hpath to create a consistent set of functionality for safe and well-typed paths. Since that includes some API breaking changes (e.g. by fixing #18) I guess it's better for me to continue there, which also allows me to move forward more quickly. |
So it turns out that I wasn't getting github notifications, I need to check why but I probably have a rogue filter somewhere. I am rather busy and not really giving any of my packages the attention they deserve (although I thought I'd already fixed #18 ). @hasufell if you're interested, why don't I add you as a collaborator and give you Hackage permissions for posix-paths? |
Well yeah, I could give it a shot and backport what I have done in the fork. |
No description provided.