2025/05/01

Newest at the top

2025-05-01 11:24:43 +0200euleritian(~euleritia@dynamic-176-006-130-078.176.6.pool.telefonica.de)
2025-05-01 11:20:14 +0200euleritian(~euleritia@77.23.248.47) (Ping timeout: 252 seconds)
2025-05-01 11:14:06 +0200Googulator65(~Googulato@2a01-036d-0106-4a24-1dc7-297e-fae3-e794.pool6.digikabel.hu)
2025-05-01 11:13:48 +0200Googulator65(~Googulato@2a01-036d-0106-4a24-1dc7-297e-fae3-e794.pool6.digikabel.hu) (Quit: Client closed)
2025-05-01 11:08:23 +0200CiaoSen(~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) CiaoSen
2025-05-01 10:58:19 +0200wootehfoot(~wootehfoo@user/wootehfoot) wootehfoot
2025-05-01 10:56:49 +0200wootehfoot(~wootehfoo@user/wootehfoot) (Read error: Connection reset by peer)
2025-05-01 10:51:18 +0200tzh_(~tzh@c-76-115-131-146.hsd1.or.comcast.net) (Quit: zzz)
2025-05-01 10:45:41 +0200lxsameer(~lxsameer@Serene/lxsameer) lxsameer
2025-05-01 10:43:40 +0200euleritian(~euleritia@77.23.248.47)
2025-05-01 10:43:23 +0200euleritian(~euleritia@dynamic-176-006-130-078.176.6.pool.telefonica.de) (Read error: Connection reset by peer)
2025-05-01 10:35:23 +0200euleritian(~euleritia@dynamic-176-006-130-078.176.6.pool.telefonica.de)
2025-05-01 10:32:21 +0200euleritian(~euleritia@ip4d17f82f.dynamic.kabel-deutschland.de) (Ping timeout: 248 seconds)
2025-05-01 10:26:14 +0200Tuplanolla(~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) Tuplanolla
2025-05-01 10:25:20 +0200CiaoSen(~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) (Ping timeout: 260 seconds)
2025-05-01 10:20:10 +0200FragByte(~christian@user/fragbyte) FragByte
2025-05-01 10:19:01 +0200FragByte(~christian@user/fragbyte) (Ping timeout: 276 seconds)
2025-05-01 10:08:36 +0200econo_(uid147250@id-147250.tinside.irccloud.com) (Quit: Connection closed for inactivity)
2025-05-01 10:03:03 +0200merijn(~merijn@77.242.116.146) merijn
2025-05-01 09:58:43 +0200gmg(~user@user/gehmehgeh) gehmehgeh
2025-05-01 09:50:02 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 252 seconds)
2025-05-01 09:48:17 +0200sajenim(~sajenim@user/sajenim) sajenim
2025-05-01 09:47:52 +0200Katarushisu(~Katarushi@finc-20-b2-v4wan-169598-cust1799.vm7.cable.virginm.net) Katarushisu
2025-05-01 09:47:09 +0200Katarushisu(~Katarushi@finc-20-b2-v4wan-169598-cust1799.vm7.cable.virginm.net) (Quit: The Lounge - https://thelounge.chat)
2025-05-01 09:46:30 +0200DigitteknohippieDigit
2025-05-01 09:45:52 +0200xff0x(~xff0x@2409:251:9040:2c00:60ef:2712:38d8:542e)
2025-05-01 09:40:56 +0200wootehfoot(~wootehfoo@user/wootehfoot) wootehfoot
2025-05-01 09:33:49 +0200jco(~jco@78-70-217-44-no600.tbcn.telia.com) (Quit: leaving)
2025-05-01 09:31:20 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-01 09:30:54 +0200rvalue(~rvalue@user/rvalue) rvalue
2025-05-01 09:29:11 +0200rvalue(~rvalue@user/rvalue) (Ping timeout: 265 seconds)
2025-05-01 09:28:59 +0200CiaoSen(~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) CiaoSen
2025-05-01 09:27:47 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Read error: Connection reset by peer)
2025-05-01 09:27:06 +0200 <tomsmeding> it does
2025-05-01 09:27:00 +0200 <haskellbridge> <hellwolf> having the proper type inference foundation helps
2025-05-01 09:26:44 +0200 <tomsmeding> s/less/fewer/
2025-05-01 09:26:39 +0200 <tomsmeding> perhaps it gets even better in a dependently-typed language; even less arbitrary restrictions
2025-05-01 09:26:35 +0200Lord_of_Life(~Lord@user/lord-of-life/x-2819915) Lord_of_Life
2025-05-01 09:25:52 +0200 <tomsmeding> somehow puzzling with all the ways you can do something to find the nicest one in haskell is not too bad, and doing the same in C++ (which is just as much of a kitchen sink) makes you want to tear your hair out
2025-05-01 09:25:08 +0200 <tomsmeding> it's great!
2025-05-01 09:25:03 +0200 <haskellbridge> <hellwolf> the fun that Haskell gives
2025-05-01 09:24:50 +0200 <haskellbridge> <hellwolf> yea, i have seen that. it's a mini type tetris game
2025-05-01 09:24:42 +0200 <tomsmeding> haskell is not a turing tarpit :p
2025-05-01 09:24:24 +0200 <tomsmeding> there are way too many ways to do it
2025-05-01 09:24:06 +0200 <haskellbridge> <hellwolf> "timtowdi", but in Haskell
2025-05-01 09:23:42 +0200 <tomsmeding> but I've seen cases where these kinds of situations can be made more readable by putting some well-chosen type variable orderings on a few functions (with explicit `forall`), resulting in the majority of the ambiguous situations being resolvable by a single type application
2025-05-01 09:23:24 +0200 <haskellbridge> <hellwolf> i use interchangeably, sometimes one style reads better than another
2025-05-01 09:22:57 +0200Lord_of_Life(~Lord@user/lord-of-life/x-2819915) (Ping timeout: 248 seconds)
2025-05-01 09:22:54 +0200 <tomsmeding> but far from always, and certainly the result is not always easier to read
2025-05-01 09:22:45 +0200 <haskellbridge> <hellwolf> yeah, there are cases where i don't care about the specific type var