2025/11/20

Newest at the top

2025-11-20 20:30:06 +0100Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net)
2025-11-20 20:29:39 +0100Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Remote host closed the connection)
2025-11-20 20:24:01 +0100wootehfoot(~wootehfoo@user/wootehfoot) wootehfoot
2025-11-20 20:18:58 +0100Nachtgespenst(~user@user/siracusa) siracusa
2025-11-20 20:18:11 +0100tromp(~textual@2001:1c00:3487:1b00:e845:fcad:fefd:4441) (Quit: My iMac has gone to sleep. ZZZzzz…)
2025-11-20 20:14:38 +0100spew(~spew@user/spew) (Quit: WeeChat 4.6.3)
2025-11-20 20:10:46 +0100peterbecich(~Thunderbi@172.222.148.214) (Ping timeout: 246 seconds)
2025-11-20 19:58:13 +0100aditya_an1l(~aditya_an@user/aditya-an1l:63825) (Ping timeout: 264 seconds)
2025-11-20 19:48:05 +0100peterbecich(~Thunderbi@172.222.148.214) peterbecich
2025-11-20 19:46:28 +0100tomboy64(~tomboy64@user/tomboy64) tomboy64
2025-11-20 19:42:40 +0100acidjnk(~acidjnk@p200300d6e71719764cede409c055dd1e.dip0.t-ipconnect.de) acidjnk
2025-11-20 19:42:00 +0100acidjnk(~acidjnk@p54ad5278.dip0.t-ipconnect.de) (Remote host closed the connection)
2025-11-20 19:39:19 +0100tomboy64(~tomboy64@user/tomboy64) (Ping timeout: 264 seconds)
2025-11-20 19:38:24 +0100Pozyomka(~pyon@user/pyon) pyon
2025-11-20 19:32:18 +0100Square3(~Square@user/square) Square
2025-11-20 19:26:28 +0100tromp(~textual@2001:1c00:3487:1b00:e845:fcad:fefd:4441)
2025-11-20 19:18:22 +0100ljdarj(~Thunderbi@user/ljdarj) ljdarj
2025-11-20 19:17:26 +0100tomboy64(~tomboy64@user/tomboy64) tomboy64
2025-11-20 19:14:56 +0100tomboy64(~tomboy64@user/tomboy64) (Ping timeout: 240 seconds)
2025-11-20 19:13:35 +0100tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net)
2025-11-20 19:13:28 +0100ft(~ft@p4fc2aaeb.dip0.t-ipconnect.de) ft
2025-11-20 19:09:49 +0100trickard(~trickard@cpe-95-98-47-163.wireline.com.au) (Ping timeout: 255 seconds)
2025-11-20 19:09:43 +0100trickard___(~trickard@cpe-90-98-47-163.wireline.com.au)
2025-11-20 19:08:11 +0100Googulator(~Googulato@85-238-67-234.pool.digikabel.hu)
2025-11-20 19:08:06 +0100tromp(~textual@2001:1c00:3487:1b00:e845:fcad:fefd:4441) (Quit: My iMac has gone to sleep. ZZZzzz…)
2025-11-20 19:07:52 +0100Googulator(~Googulato@2a01-036d-0106-0231-4475-80b4-5cdc-43d6.pool6.digikabel.hu) (Quit: Client closed)
2025-11-20 19:06:20 +0100SlackCoder(~SlackCode@remote.nationalgallery.org.ky) (Leaving)
2025-11-20 18:51:44 +0100Lycurgus(~juan@user/Lycurgus) (Quit: alsoknownas.renjuan.org ( juan@acm.org ))
2025-11-20 18:48:25 +0100annamalai(~annamalai@2409:4042:4e39:7842::9e0a:bf0a) annamalai
2025-11-20 18:48:11 +0100annamalai(~annamalai@157.32.219.191) (Read error: Connection reset by peer)
2025-11-20 18:39:24 +0100szkl(uid110435@id-110435.uxbridge.irccloud.com) (Quit: Connection closed for inactivity)
2025-11-20 18:36:07 +0100Lycurgus(~juan@user/Lycurgus) Lycurgus
2025-11-20 18:35:18 +0100jzargo(~jzargo@user/jzargo) jzargo
2025-11-20 18:34:46 +0100Googulator84Googulator
2025-11-20 18:33:38 +0100 <fgarcia> i like it though. ghc can be better at figuring out the types than i am. over half the time i will add the inferences to my source
2025-11-20 18:30:40 +0100 <fgarcia> other times if i write multiple functions without signatures and am trying to figure out why the type checker is mad, adding signatures will help narrow down the exact line causing ghc's wrath
2025-11-20 18:28:53 +0100 <fgarcia> oh, there are times when i have a function and ghci gets confused with the typing. that is what mandates the signature to me. though i also have warnings i have been ignoring too hehe
2025-11-20 18:25:16 +0100 <mauke> MR doesn't apply to this code, though
2025-11-20 18:24:35 +0100 <mauke> that's still a thing
2025-11-20 18:24:31 +0100 <probie> sam113101: In most cases you don't _need_ to, but it's generally a good idea. However with the code you've posted, you should probably write one for `nextCollatz` (if that's what you're still looking at)
2025-11-20 18:24:19 +0100 <chromoblob> there was also "monomorphism restriction" thingy, or got it changed in new GHC versions?
2025-11-20 18:23:51 +0100kuribas(~user@ip-188-118-57-242.reverse.destiny.be) (Remote host closed the connection)
2025-11-20 18:23:45 +0100 <mauke> they also help the type checker produce better error messages when something goes wrong
2025-11-20 18:23:24 +0100 <mauke> but top-level type declarations can help the human reader (i.e. me) figure out what's going on
2025-11-20 18:23:01 +0100 <mauke> in most cases types can be inferred automatically
2025-11-20 18:22:45 +0100 <chromoblob> no, not absolutely, though it may help
2025-11-20 18:21:14 +0100poscat(~poscat@user/poscat) (Ping timeout: 256 seconds)
2025-11-20 18:19:40 +0100poscat0x04(~poscat@user/poscat) poscat
2025-11-20 18:19:10 +0100chele(~chele@user/chele) (Remote host closed the connection)
2025-11-20 18:18:11 +0100 <sam113101> do I absolutely need to write the types down?