2025/09/16

Newest at the top

2025-09-16 04:07:41 +0200poscat(~poscat@user/poscat) (Ping timeout: 244 seconds)
2025-09-16 04:06:17 +0200poscat0x04(~poscat@user/poscat) poscat
2025-09-16 04:04:27 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 250 seconds)
2025-09-16 04:04:20 +0200 <StatisticalIndep> geekosaur: Amen to your comment about research papers. (I wish there was an easy way to learn what it takes to write a research paper. It seems to require a whole basket of arcane rituals to be acceptable. ;)
2025-09-16 04:04:18 +0200arandombit(~arandombi@user/arandombit) arandombit
2025-09-16 04:02:25 +0200 <StatisticalIndep> geekosaur: Though we should really get rid of that “Parsec from Temu” that forms the basis of the Read class. I actually thought it was meant to be used outside of GHC’s automatic deriving! ;)
2025-09-16 04:01:21 +0200 <StatisticalIndep> geekosaur: Parsec was a positive exception indeed. I liked it quite a lot.
2025-09-16 04:00:28 +0200 <StatisticalIndep> identifiers, of course. ;) …
2025-09-16 04:00:28 +0200 <StatisticalIndep> expected function that seems to be just missing. Without a guide, that is impossible to find! … And that the types can tell you what a function does, seems to be an old mantra, but really, even basic math operations prove that wrong. (What does (Int -> Int -> Int) do? XD) Unless you make a `type` for each of them, to give them descriptive
2025-09-16 04:00:28 +0200 <StatisticalIndep> yin: Well, the cases in point would be things like Control.Arrow, the regex libraries, the printf function, or the entire generics/SYB black magic. But even basic Foldable/Traversable have some nasty catches, where it is just implied you know that that seemingly entirely unrelated more generic function, in this case, works to do the job of a common
2025-09-16 03:59:30 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-09-16 03:57:09 +0200OftenFaded(~OftenFade@user/tisktisk) (Ping timeout: 250 seconds)
2025-09-16 03:55:37 +0200 <geekosaur> (exceptions to point (a), at least)
2025-09-16 03:55:14 +0200 <geekosaur> there are exceptions, but in many of those cases (e.g. Parsec) the "research paper" is more like a users guide anyway
2025-09-16 03:53:53 +0200 <geekosaur> also I'd note that most relevant research papers are (a) short (b) not too technical (c) quite readable
2025-09-16 03:52:39 +0200xff0x(~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp)
2025-09-16 03:52:22 +0200tabaqui(~tabaqui@167.71.80.236) tabaqui
2025-09-16 03:49:05 +0200berberman(~berberman@user/berberman) berberman
2025-09-16 03:48:29 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds)
2025-09-16 03:47:53 +0200jmcantrell_jmcantrell
2025-09-16 03:47:49 +0200jmcantrell_(~weechat@user/jmcantrell) jmcantrell
2025-09-16 03:47:21 +0200berberman(~berberman@user/berberman) (Quit: ZNC 1.10.1 - https://znc.in)
2025-09-16 03:44:08 +0200Lycurgus(~juan@user/Lycurgus) (Quit: alsoknownas.renjuan.org ( juan@acm.org ))
2025-09-16 03:43:44 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-09-16 03:38:15 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds)
2025-09-16 03:34:14 +0200 <Lycurgus> but libs have APIs and their sigs, the effective protocol implied can suffice
2025-09-16 03:33:23 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-09-16 03:33:12 +0200 <Lycurgus> in the spectrum of langs where the code is supposed to be self documenting, aside from inline and decorative comments, haskell is closer to the smalltalk end
2025-09-16 03:32:56 +0200Alleria(~Alleria@user/alleria) Alleria
2025-09-16 03:31:59 +0200Alleria(~Alleria@user/alleria) (Remote host closed the connection)
2025-09-16 03:31:50 +0200 <yin> but if you're finding documentation lacking, i'd suggest to move on to better documented library alternatives
2025-09-16 03:30:55 +0200 <yin> the language facilitates this
2025-09-16 03:30:32 +0200 <yin> not unusual. you can usually guide yourself by the types and clicking functions to see their definition
2025-09-16 03:23:00 +0200trickard_trickard
2025-09-16 03:22:26 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds)
2025-09-16 03:22:10 +0200 <StatisticalIndep> read a 50 page research paper. There should be a documentation of the intended use at the top of the page, no? … Am I missing something? Or is that just the current state of things?
2025-09-16 03:22:10 +0200 <StatisticalIndep> Hi. Can someone help me with Hackage documentation. It is way too often that I come across an important library that is entirely undocumented in the sense of how it is meant to be used, and only documented as a reference. Making is impossible to figure out the intended use. … In some cases it just points to some research papers. I don’t want to
2025-09-16 03:19:36 +0200ljdarj(~Thunderbi@user/ljdarj) (Ping timeout: 256 seconds)
2025-09-16 03:17:53 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-09-16 03:06:56 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds)
2025-09-16 02:59:50 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-09-16 02:53:22 +0200StatisticalIndep(~Statistic@2a02:3035:666:b7d5:4e00:1517:7b0c:d0aa)
2025-09-16 02:48:49 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds)
2025-09-16 02:44:01 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-09-16 02:42:35 +0200xff0x(~xff0x@2405:6580:b080:900:8846:d27a:34b2:3e5) (Ping timeout: 248 seconds)
2025-09-16 02:33:25 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds)
2025-09-16 02:27:57 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-09-16 02:22:09 +0200trickard_(~trickard@cpe-56-98-47-163.wireline.com.au)
2025-09-16 02:21:06 +0200weary-traveler(~user@user/user363627) user363627
2025-09-16 02:16:54 +0200trickard_(~trickard@cpe-56-98-47-163.wireline.com.au) (Read error: Connection reset by peer)