2024/11/01

Newest at the top

2024-11-01 14:27:32 +0100 <merijn> Step one is *having* unique codes, step two is documenting them ;)
2024-11-01 14:27:20 +0100 <merijn> mauke: Work in progress ;)
2024-11-01 14:26:48 +0100 <merijn> nice :)
2024-11-01 14:26:48 +0100 <mauke> 1 whole errors
2024-11-01 14:26:43 +0100 <mauke> hah: "So far, 1 Cabal errors and warnings are documented here."
2024-11-01 14:26:27 +0100 <merijn> I see some CABAL-xxx codes there
2024-11-01 14:26:11 +0100 <mauke> nothing there either
2024-11-01 14:25:12 +0100 <yushyin> https://errors.haskell.org/cabal/
2024-11-01 14:25:04 +0100 <merijn> mauke: https://discourse.haskell.org/t/announcing-the-haskell-error-index/5195
2024-11-01 14:25:01 +0100 <yushyin> the error message index website? yes, but it is incomplete
2024-11-01 14:24:47 +0100 <merijn> I'm assuming cabal codes are extension of that
2024-11-01 14:24:29 +0100 <merijn> mauke: Hecate was leading something on error codes in GHC
2024-11-01 14:24:17 +0100 <mauke> nothing in the manual, nothing on the website, nothing in a google search
2024-11-01 14:24:02 +0100 <mauke> merijn: I'll take that as a "no"
2024-11-01 14:23:57 +0100Square2(~Square4@user/square) Square
2024-11-01 14:23:30 +0100 <merijn> but if you run hackage you get the benefits of hyperlinked browsable docs for internal libs for free
2024-11-01 14:23:10 +0100 <merijn> Square: I think it can use "dumb" disk repos too so you could have a shared network filesystem or something and use that
2024-11-01 14:22:03 +0100slack1256(~slack1256@2803:c600:5111:8696:d97c:cbc8:139:bdb3) (Ping timeout: 244 seconds)
2024-11-01 14:21:41 +0100 <Square> is available*
2024-11-01 14:21:40 +0100Xe(~cadey@perl/impostor/xe) Xe
2024-11-01 14:21:30 +0100 <Square> merijn, yeah. Seems to be it. I was thinking there were different options. But excellent if hackage availble.
2024-11-01 14:21:15 +0100mulk(~mulk@pd95146e9.dip0.t-ipconnect.de) mulk
2024-11-01 14:20:10 +0100slac68956(~slack1256@179.60.70.224) slack1256
2024-11-01 14:19:46 +0100 <merijn> Square: You can set up your own internal Hackage and Hoogle and have cabal fallback to the regular public one (if desired)
2024-11-01 14:19:16 +0100 <merijn> Square: It uses "hackage"
2024-11-01 14:18:50 +0100 <merijn> mauke: They should be, that's the point ;)
2024-11-01 14:18:48 +0100mulk(~mulk@pd95146e9.dip0.t-ipconnect.de) (Ping timeout: 252 seconds)
2024-11-01 14:18:45 +0100 <haskellbridge> <zwro> benchmarks for trivial cases show no discernible difference
2024-11-01 14:18:05 +0100Guest77(~Guest77@2402:a00:401:f093:da9e:f3ff:fe4b:8a8b) (Quit: Client closed)
2024-11-01 14:15:53 +0100 <haskellbridge> <zwro> mauke: that makes sense. i suspect GHC might optimize to the same core implementation but i need to test it
2024-11-01 14:15:44 +0100Xe(~cadey@perl/impostor/xe) (Quit: WeeChat 4.4.2)
2024-11-01 14:12:25 +0100 <mauke> are codes like "Cabal-4345" documented anywhere?
2024-11-01 14:08:00 +0100Guest77(~Guest77@2402:a00:401:f093:da9e:f3ff:fe4b:8a8b)
2024-11-01 14:06:27 +0100 <tomsmeding> (it's nice how that head.hackage page shows how to add a 'repository' stanza to cabal.project.local, but then the cabal documentation is completely silent about such a stanza existing.)
2024-11-01 14:05:20 +0100 <Square> Gotcha. Thanks
2024-11-01 14:05:01 +0100 <Leary> Square: https://hackage.haskell.org/ says "Hackage-server is on github [...]. Developer documentation is on in the github README, includig a quick guide to running your own server instance, and mirroring the central server."
2024-11-01 14:01:37 +0100 <tomsmeding> Square: you might want to steal stuff from how head.hackage is implemented https://ghc.gitlab.haskell.org/head.hackage/
2024-11-01 14:00:47 +0100 <Square> tomsmeding, yeah i found those settings too. But what software do you use to run a repo? A company hackage if you will.
2024-11-01 13:59:00 +0100morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net) (Ping timeout: 252 seconds)
2024-11-01 13:58:16 +0100 <tomsmeding> oh there is more text in the latest version https://cabal.readthedocs.io/en/stable/cabal-project-description-file.html#cfg-field-active-reposiā€¦
2024-11-01 13:57:35 +0100 <tomsmeding> Square: https://cabal.readthedocs.io/en/3.4/cabal-project.html#cfg-field-active-repositories may be relevant, but I've never used it
2024-11-01 13:55:39 +0100euleritian(~euleritia@176.2.67.66)
2024-11-01 13:54:16 +0100morb(~morb@pool-108-41-100-120.nycmny.fios.verizon.net)
2024-11-01 13:53:31 +0100 <lambdabot> 2
2024-11-01 13:53:29 +0100 <mauke> > evalState (do error "bang"; pure 2) ()
2024-11-01 13:51:26 +0100euleritian(~euleritia@176.2.142.161) (Ping timeout: 255 seconds)
2024-11-01 13:51:19 +0100 <mauke> same, but I think the semantics of the latter depend on how IO is implemented
2024-11-01 13:45:25 +0100 <haskellbridge> <zwro> i'm still having trouble understanding the difference between (evaluate . force) and (pure @IO . ($!!))
2024-11-01 13:38:37 +0100sawilagar(~sawilagar@user/sawilagar) sawilagar
2024-11-01 13:29:49 +0100tromp(~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) (Read error: Connection reset by peer)