2025/02/02

Newest at the top

2025-02-02 03:52:18 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-02-02 03:45:39 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-02-02 03:43:20 +0100 <sim590> I'm exposing a bunch of lenses generated by haskell templates and GHC complains about lack of documentation for those. What's a common way to fix that? I can't document them if they're not in my file. Can I?
2025-02-02 03:42:57 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 248 seconds)
2025-02-02 03:38:41 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-02-02 03:34:42 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-02-02 03:30:16 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-02-02 03:30:14 +0100ensyde(~ensyde@2601:5c6:c200:6dc0::9939)
2025-02-02 03:28:05 +0100ensyde(~ensyde@2601:5c6:c200:6dc0::2163) (Ping timeout: 252 seconds)
2025-02-02 03:22:56 +0100 <haskellbridge> <Bowuigi> Cedille has a nice way to handle rewrite rules. It uses equality proofs that erase to an identity function. Extra safety and speed at the cost of extra theorem proving (after all, if you are using a theorem prover it's because you want to prove theorems). Cedille doesn't seem to insert those automatically tho, you need explicit casts
2025-02-02 03:19:18 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-02-02 03:14:54 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-02-02 03:04:31 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds)
2025-02-02 02:59:32 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-02-02 02:58:57 +0100Tuplanolla(~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) (Quit: Leaving.)
2025-02-02 02:55:21 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 265 seconds)
2025-02-02 02:50:56 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-02-02 02:48:28 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds)
2025-02-02 02:43:22 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-02-02 02:42:14 +0100 <monochrom> :)
2025-02-02 02:42:00 +0100 <int-e> I still remember when GCC broke Linux with agressive exploitation of signed overflows.
2025-02-02 02:40:45 +0100 <int-e> Yeah C also blames the programmers for introducing undefined behavior into their code.
2025-02-02 02:40:27 +0100 <Leary> But yeah, sadly too late for `Functor`.
2025-02-02 02:39:46 +0100 <Leary> I'm placing the blame solidly on the unlawful instances, and claiming only /they/ introduce undefined behaviour. :)
2025-02-02 02:39:41 +0100 <int-e> I'm not really opposed btw, except that it's hard to do this kind of thing after the fact.
2025-02-02 02:37:25 +0100 <int-e> You're introducing undefined behavior.
2025-02-02 02:36:21 +0100 <int-e> hmm but assuming properties doesn't enforce them, you're just shifting blame away from the compiler ;-)
2025-02-02 02:33:54 +0100sprotte24(~sprotte24@p200300d16f174a005425e35c82ecf678.dip0.t-ipconnect.de) (Quit: Leaving)
2025-02-02 02:33:41 +0100 <Leary> `Functor` should have gotten this treatment.
2025-02-02 02:33:34 +0100 <Leary> Break the law and GHC will punish you. >:)
2025-02-02 02:33:18 +0100 <Leary> Mmmm. Getting to write meaningful rewrite RULES is a rare and special joy, isn't it? Even better, to give a typeclass laws and declare /these laws are **enforced** by rewrite @RULES@/ in the haddocks!
2025-02-02 02:32:28 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 245 seconds)
2025-02-02 02:27:59 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-02-02 02:22:24 +0100olivial(~benjaminl@user/benjaminl) (Ping timeout: 260 seconds)
2025-02-02 02:20:42 +0100olivial_(~benjaminl@2601:1c0:847f:9c70:223:24ff:fe66:4370)
2025-02-02 02:19:55 +0100otto_s(~user@p5b0441a3.dip0.t-ipconnect.de)
2025-02-02 02:18:19 +0100otto_s(~user@p5b0448ee.dip0.t-ipconnect.de) (Ping timeout: 260 seconds)
2025-02-02 02:17:09 +0100peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 260 seconds)
2025-02-02 02:16:34 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds)
2025-02-02 02:15:46 +0100mhatta(~mhatta@www21123ui.sakura.ne.jp)
2025-02-02 02:12:08 +0100mhatta(~mhatta@www21123ui.sakura.ne.jp) (Quit: ZNC 1.9.1+deb2+b2 - https://znc.in)
2025-02-02 02:09:55 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-02-02 02:09:33 +0100acidjnk_new3(~acidjnk@p200300d6e7283f12b860008857e92372.dip0.t-ipconnect.de) (Ping timeout: 245 seconds)
2025-02-02 02:07:46 +0100olivial(~benjaminl@user/benjaminl) benjaminl
2025-02-02 02:07:39 +0100alfiee(~alfiee@user/alfiee) (Ping timeout: 244 seconds)
2025-02-02 02:06:16 +0100olivial(~benjaminl@user/benjaminl) (Remote host closed the connection)
2025-02-02 02:03:12 +0100alfiee(~alfiee@user/alfiee) alfiee
2025-02-02 02:01:12 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex) bitdex
2025-02-02 02:00:29 +0100bitdex(~bitdex@gateway/tor-sasl/bitdex) (Remote host closed the connection)
2025-02-02 01:58:51 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 246 seconds)