2025/06/13

Newest at the top

2025-06-13 15:29:35 +0200haskellbridge(~hackager@syn-096-028-224-227.res.spectrum.com) (Read error: Connection reset by peer)
2025-06-13 15:29:34 +0200ft(~ft@p3e9bc106.dip0.t-ipconnect.de) ft
2025-06-13 15:27:47 +0200ChanServ+v haskellbridge
2025-06-13 15:27:47 +0200haskellbridge(~hackager@syn-096-028-224-227.res.spectrum.com) hackager
2025-06-13 15:27:34 +0200ft(~ft@p3e9bc106.dip0.t-ipconnect.de) (Quit: Lost terminal)
2025-06-13 15:27:30 +0200Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 276 seconds)
2025-06-13 15:26:32 +0200 <tomsmeding> but if you have any such already, shoot, there's probably someone here who can answer :)
2025-06-13 15:26:18 +0200 <tomsmeding> general advice is to wait around for a couple of days and see how the discourse goes; discussion generally starts by someone asking a haskell-related question
2025-06-13 15:25:04 +0200wbooze(~inline@ip-005-146-196-202.um05.pools.vodafone-ip.de) (Quit: Leaving)
2025-06-13 15:24:16 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-06-13 15:23:53 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-06-13 15:23:45 +0200 <tomsmeding> channel activity has ups and downs; it is quiet now for a bit, but sometimes heated discussions arise :)
2025-06-13 15:22:14 +0200 <Guest66> Yep exploring it!
2025-06-13 15:22:03 +0200Guest77(~Guest77@2001:1c02:b14:e400:1ac0:4dff:fea1:7fda) ()
2025-06-13 15:21:41 +0200haskellbridge(~hackager@syn-096-028-224-227.res.spectrum.com) (Read error: Connection reset by peer)
2025-06-13 15:21:41 +0200 <tomsmeding> see the topic (probably in a box at the top of the channel log) for useful links
2025-06-13 15:21:04 +0200Guest77(~Guest77@2001:1c02:b14:e400:1ac0:4dff:fea1:7fda)
2025-06-13 15:21:03 +0200 <Guest66> I really like Haskell, and have talked with community at Reddit and FP-Discord, thought to give this UI a go xD
2025-06-13 15:20:23 +0200 <tomsmeding> Guest66: there's not much to learn, welcome :)
2025-06-13 15:19:49 +0200raym(~ray@user/raym) raym
2025-06-13 15:19:36 +0200 <mari-estel> consider the #libera channel then
2025-06-13 15:19:02 +0200 <Guest66> Hi, people its my first time interfacing a IRC client
2025-06-13 15:17:43 +0200Guest66(~Guest66@2401:4900:883f:ad86:f412:b514:54ba:e15f)
2025-06-13 15:17:05 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-06-13 15:16:43 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-06-13 15:16:25 +0200ft(~ft@p3e9bc106.dip0.t-ipconnect.de) ft
2025-06-13 15:13:57 +0200lortabac(~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4) (Ping timeout: 248 seconds)
2025-06-13 15:10:11 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-06-13 15:09:47 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-06-13 15:08:19 +0200wbooze(~inline@ip-005-146-196-202.um05.pools.vodafone-ip.de) Inline
2025-06-13 15:07:53 +0200wbooze(~inline@ip-005-146-196-202.um05.pools.vodafone-ip.de) (Remote host closed the connection)
2025-06-13 15:05:07 +0200Achylles(~Achylles@45.182.57.28) Achylles
2025-06-13 15:02:21 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-06-13 15:01:59 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-06-13 14:54:58 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-06-13 14:54:34 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-06-13 14:53:37 +0200target_i(~target_i@user/target-i/x-6023099) target_i
2025-06-13 14:50:06 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-06-13 14:49:58 +0200 <tomsmeding> but there can be value in discussing how to make low-effort documentation as useful as possible, because realistically, a decent fraction of code on hackage is going to have low-effort documentation only :p
2025-06-13 14:49:40 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Remote host closed the connection)
2025-06-13 14:49:19 +0200 <tomsmeding> ideally you have various different kinds of documentation for various different audiences and consumption styles, yes
2025-06-13 14:48:55 +0200AlexZenon(~alzenon@178.34.163.76)
2025-06-13 14:48:41 +0200 <kuribas`> tomsmeding: my take is that you need both, but also different forms of documentation, based on usecase, references, guides, overviews, getting-started, etc...
2025-06-13 14:47:07 +0200acidjnk(~acidjnk@p200300d6e71c4f374cafb09973b7f579.dip0.t-ipconnect.de) acidjnk
2025-06-13 14:46:13 +0200tmciver(~tim@syn-198-255-177-240.res.spectrum.com) tmciver
2025-06-13 14:46:12 +0200sajenim(~sajenim@user/sajenim) sajenim
2025-06-13 14:46:06 +0200mari-estel<3 doctests
2025-06-13 14:45:45 +0200 <tomsmeding> kuribas`: I guess, yes :p
2025-06-13 14:45:39 +0200tmciver(~tim@syn-198-255-177-240.res.spectrum.com) (Ping timeout: 268 seconds)
2025-06-13 14:45:25 +0200 <kuribas`> tomsmeding: you can reverse that: "it's rare documentation is simultaneously so precise and so general that without any types you can fully understand what a function does"