Roman Cheplyaka

Thanks for the offer @alexbiehl. The task list would be roughly as follows: - [ ] do a general code review - [ ] test (by hand) that it works...

@coot thanks, good catch, we definitely don't want that. I guess we can always go through unsafePerformIO; are there any better ideas? Might ask QuickCheck devs what they think.

In general, I tend to agree with these advantages. However, the XDG spec seems to be designed with typical desktop application in mind, not compilers or package managers. As @dcoutts...

> Users binaries, documentation and libraries are users data and thus should go to $XDG_DATA_HOME (which default to ~/.local/share), Yes, that's exactly what I meant by the desktop application oriented...

Whether it is better or not is out of the scope of this issue, I believe.

So that would be `~/.local/share/cabal/bin`, which looks rather disappointing to anyone who ever cares about what these paths are. I think at this point it would be more realistic for...

I think addDynamicLibrarySearchGeneratorForCurrentProcess might be doing more or less the same thing in your case as loadLibraryPermanently. Try (a) removing both calls and (b) removing addDynamicLibrarySearchGeneratorForCurrentProcess but leaving loadLibraryPermanently and...

Does [this](https://hackage.haskell.org/package/parser-combinators-1.2.0/docs/Control-Applicative-Combinators.html#v:count-39-) do what you want? I'd accept a PR explaining (in the haddocks) how to do this for others who may be looking for the same thing.

Ah, good point. In that case it may be worth defining our own function.

Have you seen the `count` combinator linked above?