cleff VS hackage-server

I ended up using a different approach to guiding inference in my project, but I still thought the IP way was cool

Consider 2 Haskell projects: Cleff and Effectful. They both are extensible effect systems, built around ReaderT design pattern. At their core, they use fused ReaderT + IO monad, with extensible environment. This architecture is very similar to ZIO's. All 3 even share the same limitation - inability to express nondeterminism (not very relevant fact, but I just want to emphasize the similarity).

cleff and effectful are very similar, to the point that I offered to join forces (for the record, majority of the conversation refers to things that are no longer true for both libraries as we inspired each other to fix most quirks :). The main difference is the internal environment - in effectful it's mutable, while in cleff it's immutable. All differences pretty much grow from this. The main ones:

I'm pleased to announce cleff, a new extensible effects library for Haskell: https://github.com/re-xyr/cleff.

Very cool! Is this open-source? It would be cool to add a few sources to this (like https://hackage.haskell.org).

Selected mirror http://hackage.haskell.org/

3. https://hackage.haskell.org is the primary place

I used to see pandoc described as a "virus that makes people want to install Haskell", but I think someone must've figured out binary distribution.

The closest analogue to ZIO is probably the RIO monad + Has* type classes from https://hackage.haskell.org . /package/rio . (But ZIO is a bit richer with the typed error channel.)

Not yet, first hackage-server has to be updated to Cabal-3.8.1.0, see this hackage-server ticket

So I was working on this tool pysearch.com for doing deep semantic searches of python docs by program analysis inferred functionality when I noticed that every library's docs seem to be in a different format hosted in a different source. This would be fine if there was also a standard format hub for all the libraries on pypi or something, but it looks like even readthedocs doesn't contain everything. I find this a bit odd given the existence of tools like pydoc for doing something like this locally. Originally, I was hoping to find something like hackage for haskell, as I was hoping to build a natural language version of hoogle. In the meantime I've gotten pysearch to work by setting up custom rules for each doc, but this is kinda unsustainable.

$ cabal get network-into -v3 ... /usr/bin/curl 'http://hackage.haskell.org/package/network-info-0.2.1.tar.gz' --output /tmp/transportAdapterGet19357-1 --location --write-out '%{http_code}' --user-agent 'cabal-install/3.6.2.0 (linux; x86_64)' --silent --show-error --dump-header /tmp/curl-headers19357-2.txt Exception Unexpected response 503 for http://hackage.haskell.org/package/network-info-0.2.1.tar.gz when using mirror http://hackage.haskell.org/ Selected mirror http://hackage.fpcomplete.com/Downloading package network-info-0.2.1/usr/bin/curl 'http://hackage.fpcomplete.com/package/network-info-0.2.1.tar.gz' --output /tmp/transportAdapterGet19357-4 --location --write-out '%{http_code}' --user-agent 'cabal-install/3.6.2.0 (linux; x86_64)' --silent --show-error --dump-header /tmp/curl-headers19357-5.txt Exception Unexpected response 503 for http://hackage.fpcomplete.com/package/network-info-0.2.1.tar.gz when using mirror http://hackage.fpcomplete.com/ Selected mirror http://objects-us-east-1.dream.io/hackage-mirror/ Downloading package network-info-0.2.1/usr/bin/curl 'http://objects-us-east-1.dream.io/hackage-mirror/package/network-info-0.2.1.tar.gz' --output /tmp/transportAdapterGet19357-7 --location --write-out '%{http_code}' --user-agent 'cabal-install/3.6.2.0 (linux; x86_64)' --silent --show-error --dump-header /tmp/curl-headers19357-8.txt Unexpected response 403 for http://objects-us-east-1.dream.io/hackage-mirror/package/network-info-0.2.1.tar.gz

See https://github.com/haskell/hackage-server/issues/997.

The other source of haskell documentation is hackage, which features both libraries and higher-level GHC modules. Using hoogle (!hoogle or !hgl in DDG), you can search these docs by module name, function name, or even type signature.