2025/04/01

Newest at the top

2025-04-01 19:16:18 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 244 seconds)
2025-04-01 19:15:56 +0200Smiles(uid551636@id-551636.lymington.irccloud.com) Smiles
2025-04-01 19:14:36 +0200zungi(~tory@user/andrewchawk) (Ping timeout: 264 seconds)
2025-04-01 19:10:31 +0200Natch(~natch@c-92-34-7-158.bbcust.telenor.se) (Remote host closed the connection)
2025-04-01 19:06:48 +0200CiaoSen(~Jura@2a02:8071:64e1:da0:5a47:caff:fe78:33db) CiaoSen
2025-04-01 18:59:14 +0200ft(~ft@p508db463.dip0.t-ipconnect.de) ft
2025-04-01 18:57:24 +0200ft(~ft@p508db463.dip0.t-ipconnect.de) (Client Quit)
2025-04-01 18:52:45 +0200ft(~ft@p508db463.dip0.t-ipconnect.de) ft
2025-04-01 18:46:06 +0200acidjnk_new(~acidjnk@p200300d6e71c4f82640579a6e00084b6.dip0.t-ipconnect.de) (Ping timeout: 246 seconds)
2025-04-01 18:45:14 +0200ubert(~Thunderbi@2a02:8109:ab8a:5a00:74f1:1caf:2629:a3c8) (Remote host closed the connection)
2025-04-01 18:42:59 +0200kawzeg(kawzeg@2a01:7e01::f03c:92ff:fee2:ec34) kawzeg
2025-04-01 18:38:58 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich
2025-04-01 18:35:05 +0200kawzeg(kawzeg@2a01:7e01::f03c:92ff:fee2:ec34) (Quit: WeeChat 4.3.0)
2025-04-01 18:34:45 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 276 seconds)
2025-04-01 18:31:18 +0200danza(~danza@user/danza) (Remote host closed the connection)
2025-04-01 18:29:42 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich
2025-04-01 18:29:18 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 246 seconds)
2025-04-01 18:26:55 +0200aman(~aman@user/aman) aman
2025-04-01 18:24:53 +0200aman(~aman@user/aman) (Ping timeout: 252 seconds)
2025-04-01 18:20:33 +0200machinedgod(~machinedg@d108-173-18-100.abhsia.telus.net) (Ping timeout: 248 seconds)
2025-04-01 18:19:59 +0200merijn(~merijn@77.242.116.146) (Ping timeout: 244 seconds)
2025-04-01 18:15:32 +0200danza(~danza@user/danza) danza
2025-04-01 18:14:48 +0200ChanServ+v haskellbridge
2025-04-01 18:14:48 +0200haskellbridge(~hackager@syn-024-093-192-219.res.spectrum.com) hackager
2025-04-01 18:12:02 +0200peterbecich(~Thunderbi@syn-047-229-123-186.res.spectrum.com) peterbecich
2025-04-01 18:11:51 +0200haskellbridge(~hackager@syn-024-093-192-219.res.spectrum.com) (Remote host closed the connection)
2025-04-01 18:10:41 +0200tomsmedingis afk for a while
2025-04-01 18:09:52 +0200 <hellwolf> right. i didn't realize it was closed and fixed.
2025-04-01 18:09:36 +0200 <tomsmeding> you can indeed reply to the same issue; it's likely that you'll subsequently be instructed to create a new issue instead
2025-04-01 18:09:00 +0200 <hellwolf> 9.10
2025-04-01 18:08:56 +0200 <tomsmeding> the fix for that PR is in 9.6; what GHC version are you using?
2025-04-01 18:08:44 +0200 <hellwolf> I see, indeed. I might as well report one more sample to the same issue.
2025-04-01 18:08:04 +0200 <tomsmeding> this actually sounds extemely related to https://gitlab.haskell.org/ghc/ghc/-/issues/22057
2025-04-01 18:07:17 +0200 <hellwolf> mxs_ & mxs_'
2025-04-01 18:07:08 +0200 <hellwolf> https://paste.tomsmeding.com/wRfhejVB
2025-04-01 18:06:48 +0200tomsmedingsuspects mx1_
2025-04-01 18:06:36 +0200 <hellwolf> let me find the error message, one sec
2025-04-01 18:06:19 +0200 <tomsmeding> which variable do you get a warning about?
2025-04-01 18:05:57 +0200 <hellwolf> here: https://paste.tomsmeding.com/JU7QBp5w
2025-04-01 18:05:53 +0200 <tomsmeding> in general, if there's an issue in GHC, do report it; that's what the issue tracker is for
2025-04-01 18:05:25 +0200 <tomsmeding> what is the case? Is it reasonable for GHC to detect it?
2025-04-01 18:05:22 +0200 <int-e> the other versions do exist :)
2025-04-01 18:04:55 +0200 <hellwolf> Considering the number of GHC issues, I don't think I should report and create one more issue there, for now.
2025-04-01 18:04:55 +0200 <hellwolf> I had a minor bug, I used bang pattern in a TH quote, and GHC complaining that I have unused variable, but I clearly used it.
2025-04-01 18:04:30 +0200 <int-e> good catch, thanks
2025-04-01 18:04:22 +0200 <tomsmeding> ah
2025-04-01 18:04:19 +0200 <int-e> so it fell back on 9.6.6
2025-04-01 18:04:16 +0200 <tomsmeding> what did it do :p
2025-04-01 18:04:09 +0200 <int-e> I don't actually have 9.12.2 built, /opt/ghc-9.12.2 is empty
2025-04-01 18:03:36 +0200 <int-e> oh that's my bad