2026/02/11

Newest at the top

2026-02-11 18:41:18 +0100tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net)
2026-02-11 18:40:17 +0100karenw(~karenw@user/karenw) (Ping timeout: 250 seconds)
2026-02-11 18:39:47 +0100 <perryprog> I'm having some trouble troubleshooting a build failure—I'm getting "The build process segfaulted" from cabal and I'm not seeing much help from cabal build -v (https://paste.tomsmeding.com/aGOsdU5i). The project is https://github.com/pdobsan/oama. There's reports of this sort of build failure from a few years ago also on macOS, but that was from an older macOS version and also seems to have been fixed...
2026-02-11 18:37:52 +0100 <haskellbridge> <sm> if by <file> you mean a shake target
2026-02-11 18:37:25 +0100 <haskellbridge> <sm> __monty__ I think that's implied, isn't it ? Shake's dependency engine will do that by default
2026-02-11 18:36:38 +0100perryprog(~perryprog@wikipedia/perryprog) perryprog
2026-02-11 18:35:33 +0100tromp(~textual@2001:1c00:3487:1b00:5913:697:5f95:d198)
2026-02-11 18:35:23 +0100Guest2(~Guest2@client-8-178.eduroam.oxuni.org.uk)
2026-02-11 18:31:51 +0100tromp(~textual@2001:1c00:3487:1b00:5913:697:5f95:d198) (Quit: My iMac has gone to sleep. ZZZzzz…)
2026-02-11 18:28:24 +0100ft(~ft@p508db4c0.dip0.t-ipconnect.de) ft
2026-02-11 18:27:40 +0100edwardk(sid47016@haskell/developer/edwardk) edwardk
2026-02-11 18:27:39 +0100 <yin> what's "it"?
2026-02-11 18:27:31 +0100 <yin> in what context?
2026-02-11 18:27:28 +0100edwardk(sid47016@haskell/developer/edwardk) (Server closed connection)
2026-02-11 18:22:59 +0100diabloblanco(~diablobla@user/diabloblanco) (Remote host closed the connection)
2026-02-11 18:22:19 +0100smalltalkman(uid545680@id-545680.hampstead.irccloud.com) smalltalkman
2026-02-11 18:22:08 +0100smalltalkman(uid545680@id-545680.hampstead.irccloud.com) (Server closed connection)
2026-02-11 18:19:55 +0100lxsameer(~lxsameer@Serene/lxsameer) (Ping timeout: 246 seconds)
2026-02-11 18:16:31 +0100 <__monty__> Shake question, is there a concept of recursively "need"ing a file? What I mean is having a rule declare it `need`s <file> but in addition to rebuilding if <file> changes, it will also be rebuilt if any dependency of <file> has changed?
2026-02-11 18:14:52 +0100 <yin> look, smartphones were great and all but i miss typing on old nokias
2026-02-11 18:12:37 +0100merijn(~merijn@77.242.116.146) (Ping timeout: 264 seconds)
2026-02-11 18:11:40 +0100tomsmeding. o O ( goid, halfway between good and gold )
2026-02-11 18:11:20 +0100 <yin> i think is was streamly
2026-02-11 18:10:22 +0100 <mauke> streaming?
2026-02-11 18:10:07 +0100prdak(~Thunderbi@user/prdak) (Read error: Connection reset by peer)
2026-02-11 18:09:42 +0100marinelli(~weechat@gateway/tor-sasl/marinelli) marinelli
2026-02-11 18:09:23 +0100marinelli(~weechat@gateway/tor-sasl/marinelli) (Remote host closed the connection)
2026-02-11 18:08:51 +0100prdak(~Thunderbi@user/prdak) prdak
2026-02-11 18:08:30 +0100prdak(~Thunderbi@user/prdak) (Read error: Connection reset by peer)
2026-02-11 18:07:52 +0100 <probie> streamly?
2026-02-11 18:07:45 +0100jmcantrell_jmcantrell
2026-02-11 18:07:42 +0100 <yin> there was another one i used which had goid performance, can't recall its name. something with 's'...?
2026-02-11 18:07:14 +0100prdak(~Thunderbi@user/prdak) prdak
2026-02-11 18:06:42 +0100prdak1(~Thunderbi@user/prdak) (Ping timeout: 256 seconds)
2026-02-11 18:05:31 +0100 <merijn> If you're operating on data coming from disk/network, etc. that's gonna be entirely unimportant
2026-02-11 18:04:53 +0100 <merijn> The main "problem" it has, is that it's not really tuned for super efficiency
2026-02-11 18:04:22 +0100 <merijn> It's the only one I really used extensively
2026-02-11 18:04:15 +0100 <merijn> probie: conduit is fine
2026-02-11 18:02:23 +0100prdak1(~Thunderbi@user/prdak) prdak
2026-02-11 18:02:18 +0100prdak(~Thunderbi@user/prdak) (Read error: Connection reset by peer)
2026-02-11 18:01:28 +0100prdak(~Thunderbi@user/prdak) prdak
2026-02-11 17:59:26 +0100 <probie> s/too big fit/too big to fit/
2026-02-11 17:58:28 +0100 <probie> I've just got some lazy bytestrings that are much too big fit in memory and want some guard rails so I don't accidentally cause a space leak. I figure conduit gives me that if my only direct usage of them are in calls to `yieldMany`
2026-02-11 17:48:33 +0100wickedjargon(~user@24.83.46.194) wickedjargon
2026-02-11 17:47:15 +0100jmcantrell_(~weechat@user/jmcantrell) jmcantrell
2026-02-11 17:43:40 +0100dyniec(~dyniec@dybiec.info) dyniec
2026-02-11 17:43:28 +0100dyniec(~dyniec@dybiec.info) (Server closed connection)
2026-02-11 17:40:18 +0100Googulator(~Googulato@2a01-036d-0106-216f-6164-ec92-51a0-9cde.pool6.digikabel.hu)
2026-02-11 17:40:04 +0100Googulator(~Googulato@2a01-036d-0106-216f-6164-ec92-51a0-9cde.pool6.digikabel.hu) (Quit: Client closed)
2026-02-11 17:38:12 +0100marinelli(~weechat@gateway/tor-sasl/marinelli) marinelli