Neil Mitchell
Neil Mitchell
Specifically should benchmark operations against utf8-string, bytestring, text and vector. Ideally would be best-of-breed on all of those, and quite an easy criterion to write.
When reviewing the Shake normalise function, I realised the implementation I had was all wrong. I should backport the appropriate Shake tests to the FilePath library and see if that...
Pulling out from https://github.com/haskell/filepath/issues/12#issuecomment-64000192, I think most path/drive based functions (but not extension functions) should first parse their path, then modify, then render it. That gives a much smaller "trusted...
In the Windows version of the API, `"//foo" "txt" == "//foo\\.txt"`. That's not what anyone expects, and doesn't match the .NET conventions for filepaths. It also means Shake can't use...
Two useful properties of filepath operators are being idempotent (as you might hope `normalise` was) and being valid lenses, specifically obeying: ``` view l (set l b a) = b...
Migrated from https://ghc.haskell.org/trac/ghc/ticket/8752: ## @joeyh said: "Combine two paths, if the second path isAbsolute, then it returns the second." But, the implementation of combine checks if the first character of...
``` writeFile "foo " "" writeFile "bar" "" doesFileExist "foo" -- True doesFileExist "foo " -- True doesFileExist "bar " -- True ``` Seemingly any trailing spaces in a path...
At the moment the docs are awful since you get a massive list of modules that you can't search through. Make the modules such as `Opaleye.Operators` hidden so that `Opaleye`...
As a consumer of product-profunctors, this impacts OpalEye. You should probably turn on issues and migrate from https://github.com/karamaan/product-profunctors/issues
.== returns NULL if one of its arguments is NULL but the type does not reflect this.