2026/02/23

Newest at the top

2026-02-23 12:47:54 +0100 <Leary> No, instances have this funny property that they're automatically imported and re-exported by every module they touch. If the instance isn't an orphan you're cooked.
2026-02-23 12:47:40 +0100xnyhps(~xnyhps@s.xnyhps.nl)
2026-02-23 12:47:26 +0100xnyhps(~xnyhps@s.xnyhps.nl) (Server closed connection)
2026-02-23 12:46:17 +0100jonrh(sid5185@id-5185.ilkley.irccloud.com) jonrh
2026-02-23 12:46:06 +0100jonrh(sid5185@id-5185.ilkley.irccloud.com) (Server closed connection)
2026-02-23 12:44:35 +0100 <Milan_Vanca> Ty Leary
2026-02-23 12:44:32 +0100 <Milan_Vanca> I will try to not import whole module but only needed parts, then as Instances are not imported it might work I guess?
2026-02-23 12:43:34 +0100 <Milan_Vanca> 9u
2026-02-23 12:42:47 +0100energizer(~energizer@user/energizer) energizer
2026-02-23 12:42:16 +0100cawfee(root@2401:c080:3800:3460::babe) qjqqyy
2026-02-23 12:42:06 +0100energizer(~energizer@user/energizer) (Server closed connection)
2026-02-23 12:41:57 +0100cawfee(root@2401:c080:3800:3460::babe) (Server closed connection)
2026-02-23 12:33:41 +0100L29Ah(~L29Ah@wikipedia/L29Ah) ()
2026-02-23 12:33:23 +0100 <Leary> Milan_Vanca: Instances must be unique. Unless the other instance is an orphan you can avoid importing, all you can do is give your instance to a newtype over `ByteString`.
2026-02-23 12:30:07 +0100 <Milan_Vanca> Hi guyz! How to solve "duplicate instance declarations"? Data.ByteString.Lazy.Char8 defines IsString ByteString instance. Which I don't like as it truncates. I want proper utf8 implementation so I implemented another instance like fromString = TextLazyEncoding.encodeUtf8 . TextLazy.pack My intent is to start using OverloadedStrings byt with my instance.
2026-02-23 12:29:01 +0100fp(~Thunderbi@130.233.70.214) fp
2026-02-23 12:22:20 +0100Milan_Vanca(~milan@user/Milan-Vanca:32634) Milan_Vanca
2026-02-23 12:20:38 +0100Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net)
2026-02-23 12:20:29 +0100edwtjo(~edwtjo@fsf/member/edwtjo) edwtjo
2026-02-23 12:20:29 +0100edwtjo(~edwtjo@h-155-4-52-89.A213.priv.bahnhof.se) (Changing host)
2026-02-23 12:20:29 +0100edwtjo(~edwtjo@h-155-4-52-89.A213.priv.bahnhof.se)
2026-02-23 12:20:06 +0100edwtjo(~edwtjo@fsf/member/edwtjo) (Server closed connection)
2026-02-23 12:19:44 +0100[_________](~oos95GWG@user/oos95GWG) oos95GWG
2026-02-23 12:19:37 +0100Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 248 seconds)
2026-02-23 12:19:26 +0100[_________](~oos95GWG@user/oos95GWG) (Server closed connection)
2026-02-23 12:18:40 +0100terrorjack(~terrorjac@2a01:4f8:271:2d98::2) terrorjack
2026-02-23 12:18:31 +0100koz(~koz@121.99.240.58) (Ping timeout: 255 seconds)
2026-02-23 12:16:11 +0100koz_(~koz@121.99.240.58)
2026-02-23 12:15:00 +0100fp(~Thunderbi@130.233.70.214) (Ping timeout: 256 seconds)
2026-02-23 12:14:49 +0100 <kuribas> If there is more interest, I'll probably need to port it to python or so...
2026-02-23 12:14:26 +0100 <kuribas> No, just my organisation.
2026-02-23 12:14:03 +0100 <comerijn> kuribas: Is this for other dev's in general or just for, for example, people within your organisation?
2026-02-23 12:13:27 +0100 <comerijn> See musl, which is used by Alpine
2026-02-23 12:13:25 +0100 <__monty__> An archive with a dynamic executable and all the necessary libraries is another option.
2026-02-23 12:13:07 +0100 <comerijn> There are other libc's that work just fine
2026-02-23 12:12:59 +0100 <comerijn> The problem with libc is GNU libc intentionally breaking static linking
2026-02-23 12:12:33 +0100 <comerijn> kuribas: Depends which libc you use
2026-02-23 12:12:14 +0100 <kuribas> comerijn: Doesn't that come with libc problems on linux?
2026-02-23 12:11:52 +0100 <comerijn> kuribas: I'd say static binary
2026-02-23 12:11:52 +0100 <kuribas> Maybe I could try a dev container, where he can build and maybe develop on the app.
2026-02-23 12:11:27 +0100Leary(~Leary@user/Leary/x-0910699) Leary
2026-02-23 12:11:24 +0100 <__monty__> I'd personally prefer a flatpak to a docker container, especially for a tool rather than a service.
2026-02-23 12:11:20 +0100SoF(~skius@user/skius) skius
2026-02-23 12:10:46 +0100SoF(~skius@user/skius) (Server closed connection)
2026-02-23 12:09:58 +0100 <tomsmeding> ah I may have tried something other than docker back then
2026-02-23 12:09:29 +0100 <tomsmeding> I've tried the alpine approach once and it didn't work for me, but then perhaps I didn't try enough / failed somehow
2026-02-23 12:09:06 +0100 <tomsmeding> kuribas: you might look at https://cs-syd.eu/posts/2024-04-20-static-linking-haskell-nix or https://hasufell.github.io/posts/2024-04-21-static-linking.html
2026-02-23 12:09:03 +0100 <kuribas> But docker is more common that ghc (cabal/stack/ghcup) installation.
2026-02-23 12:07:51 +0100 <__monty__> If you give me a docker for example, now I need to install and then figure out how to use podman.
2026-02-23 12:07:26 +0100 <__monty__> A distro-specific package is the only thing I can come up with that ticks the easiest for them box but then it depends on how many distros you'd want to target.